Add support of sensor manager in InputDevice and allow user to obtain
SensorManager object to query supported sensor types and register sensor
event listeners.
Bug: 161634265
Test: atest InputDeviceSensorManagerTest
Change-Id: Ia7a04a0fcf7e026c49a4fb1a9009b132ff84cf7c
After getting enough feedback from dogfooders, the issues left open that
we know of (that will still be addressed ofc) either don't hurt dogfood
experience (eg. b/172627742 touch is blocked only during AGSA's -1
screen <> launcher side animation) or are 3p apps that will have to
change their code at some point. So, turning the feature on in its final
enforcing mode.
Also removing toast since at this point this is more noise than signal.
We're seeing many duplicate bugs (many of which are WAI) that the
dogfooder would likely not notice if it wasn't for the toast. If there
is a real issue the user will still notice by the unresponsiveness and
given a bugreport we will be able to check via logcat.
However, I have not removed the code completely and left that as part
of b/169067926 since we may decide to turn it back on before or on
DP/Beta.
Bug: 158002302
Test: Verify untrusted touches are blocked via logcat but no toast.
Change-Id: Ic66ce0dc273fae3f1d974dd46d383f046f78e485
This CL relays requests to enable or disable Pointer Capture in
InputManagerService to InputDispatcher.
Windows now request Pointer Capture using their InputChannel token
instead of their IWindow tokens.
Bug: 141749603
Test: manual: flash crosshatch, test pointer capture.
Change-Id: Ic6fc01eae0068dfbba496051d988a71bcabcd0b3
SystemApi complains:
error: Constant field names must be named with only upper case characters:
`android.hardware.hdmi.HdmiControlManager#HDMI_CEC_VERSION_1_4_b`,
should be `HDMI__CEC__VERSION_1_4_B`
Bug: 174731501
Bug: 172637440
Test: atest com.google.android.gts.hdmicec.HdmiControlManagerHostTest
Change-Id: Ia1bfdb44e704c99fa574663f658a2173f6b48d21
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
