After Treble's FLP merge into GNSS HAL, the FlpHardwareProvider is just
an empty shell. Removing FusedLocation and/or Flp + Hardware classes
altogether.
Bug: 35726697
Test: m -j
Test: Open Google Map and then walk around. The dot moves as I walk.
Merged-In: I7f413e38b57424e8ebb9d7d14d94f145a48d10f8
Change-Id: I7f413e38b57424e8ebb9d7d14d94f145a48d10f8
(cherry picked from commit 4cc3a1c056)
Cherry-pick from 30b9adfad1
The screen unlocked functions save effort on setting
the usb config during each connection. These
functions persist between connections and between
boots. When the screen is unlocked and these
functions are set, the current functions will
be automatically set to the screen unlocked functions.
Also added svc command for this so it can be
used and tested while the UI is worked on.
Bug: 62876645
Test: svc usb setScreenUnlockedFunctions mtp
Test: Test functions with locking, unlocking, and
disconnecting, with no lockscreen, swipe, and pattern
Change-Id: Ia05e095917166d25398c4d310b02971e3a1bb12a
display need to be destroyed once the display is removed.
Then apply this flag to VR virtual display.
Change-Id: Icb5aa1280b6ebac5941afda1cc1b94b258ce44f4
Bug: 67420451
Test: Manually. "adb shell am stack list" does not show contents
from virtual display anymore after it's released.
Fix following types of issue
* over 100 char/line
* missing space
* trailing spaces
* array bracket position
* variable naming convention (some cases)
* indentation
* long expression wrapping operator position
* missing curly brace for one line scope
* function modifier order
Things not changed in this CL:
* Redundant public modifiers.
* A few local variable names.
* Suggested @deprecate but function is actually @removed.
Test: m and m docs
Change-Id: I5c22648888487edaa5954026a166cfd810a8a912
Java doc was left out when addressing API reviewer comments.
This CL fix the discrepancy between the actual logic and java doc.
Bug: 36550285
Test: compiles
Change-Id: I6406892ecdcc5d02f11966fa3fb0b81ed8d3b285
Merged-In: I6406892ecdcc5d02f11966fa3fb0b81ed8d3b285
- Since mHandle (UID) was not recorded in writeToParcel, it always
returned 0 as the UID. This resulted in error messages claiming
mismatches between the reported and actual UID of nanoapps when called
from an external process.
- Also fixes the Parcel constructor to actually read the mContexthubId
field.
Bug: 37785458
Test: Compile and load, verify error message doesn't appear
Change-Id: I2ff75f510aae549c741786f5746862256ea5a877
Explictly use Locale.US since EXIF/TIFF date/time fields require it.
Test: Switch to Arabic locale, verify no crash and resulting DNGs have valid metadata,
plus CTS DngCreatorTest passes.
Bug: 65748590
Change-Id: I729ee6d849f7a39e5d396cfd8dd5d44325381822
The deprecated camera API throws a lot of RuntimeExceptions, and many of the
methods don't mention this.
Test: Docs build and manual review
Bug: 64725721
Change-Id: I1c6dc2f984d0be8b0d4b5394bb0d7473dfec7949
This adds FINGERPRINT_ERROR_USER_CANCELED to the list of possible errors
returned by FingerprintManager.authenticate().
Fixes b/64540509
Test: documentation builds
Change-Id: I66b46d385ab10eb0bc8e982c06e7a60570a79165
SurfaceView created for on-screen preview sometimes loses
transformation information in the Camera2 API with HALv1
environment, and therefore produced wrongly transformed frames.
It's because in RequestThreadManager.configureOutputs(), the
transformation set by LegacyCameraDevice.setSurfaceOrientation()
is cleared at mGLThreadManager.setConfigurationAndWait().
The bug is fixed by setting transformation information again
after mGLThreadManager.setConfigurationAndWait().
BUG=63313861
TEST=Check on minnie with GCA and CameraIQTesting app. Preview always
displays correct transformation in Camera2<=>HALv1 environment.
Change-Id: Ic395047a120a21b3968dedb4314bdbe519c932e6
onRequestQueueEmpty callback needs to be supported for legacy HAL1
devices.
Test: Camera CTS
Bug: 64483624
Change-Id: I268a1fe7577788c4e4e13dfecd7bb7abe0d82e6c
This solves a problem of identifying, if a given application is talking
to a hardware that can handle format of these strings.
Bug: b/64229617
Test: VTS, instrumentation
Change-Id: I6f525be90105bfdc01a899feea2a3151719ec8d2
Per the documentation, the input surface of a reprocessable capture
session should be abandoned on the close of a session.
Actually implement this, to avoid unintentional leaks of buffers.
Test: Camera CTS passes
Bug: 38313948
Change-Id: Ia45c39ea925288a5082d6e722ff4b40c55971a37
STILL_CAPTURE, RECORD, and VIDEO_SNAPSHOT templates are not
guaranteed on depth only devices.
Test: make docs
Bug: 64157646
Change-Id: I1b2db9d919e136d640be0ca04f63b71e4603e542
New version of ActivityView that doesn't use expensive
ActivityContainer, but utilizes VirtualDisplays instead.
Creation of this view is only allowed for callers who have
android.Manifest.permission.INJECT_EVENTS permission.
Launching activities into this container is restricted by
the same rules that apply to launching on VirtualDisplays:
- Owner is allowed to launch its own activities.
- If activity that's being launched is not from the same
app, then it must be embeddable and launcher must have
permission to embed.
Bug: 63338670
Test: go/wm-smoke
Change-Id: Id9a25752367ebe8e59d2fc21c5d9de5cf597ea01
