- Move camera reference doc images to /reference/images
- Minor formatting changes due to merging SDK/NDK metadata definitions
- Minor wording changes for the same
Bug: 69175492
Bug: 29102963
Bug: 33262893
Test: Build and manual inspection of generated docs diff
Change-Id: Ieaf0c1943eba378cc94a22d184734602c40e25e7
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
Two new methods within camera capture session will allow clients to
attach and remove shared output surfaces to a live camera session
dynamically.
Test: Camera CTS
Bug: 63912484
Change-Id: I291fc2b558fc62f7dc8072e57f5ff831d46e765c
Each USB device can have one default handler. This app is launched when
the device is plugged in. A default handler automatically gets
permission to access the device when launched.
All other apps have to request the permission to access the USB device
via UsbManager.requestPermission. In the permission dialog there is an
option to make the app the default app for the device. Of course this
only makes sense if this app declares the right properties to be
auto-launched. Hence check this and only then show this options.
Also made the string in the dialogs easier to understand.
AccessoryFilter and DeviceFilter needed to be copied so I can access
them from system-ui. No code change in these classes.
Test: requested permissions from app that could by the default for the
device and from an app that could not. Also tested "confirm" flow
that is executed when the device is plugged in and a app that
might be default is installed.
Bug: 67381583
Change-Id: I12eb7efed0ad107c70ae32433a5629108f252486
Needed at the service when creating the app binary object to send to the
Context Hub.
Bug: 67734082
Test: Make from root
Change-Id: I4395fb1229fe384ffd5b2f7c3ba49152584a753d
Creates a IContextHubTransactionCallback, a callback that can be invoked
at the service as a proxy after completion of each transaction. The
ContextHubManager generates the callback for every transaction, and
passes it down to the service. This removes the need for the transaction
ID to be tracked at the client application side.
Bug: 67734082
Test: Make from root
Change-Id: I89a77a308671e7a84e50b27eb9c4de012dedc310
Per feedback from dmail@, rephrased to clarify that the intent is
fired at the time when a USB device/accessory is attached, not a
general "a USB device happens to be attached now" notification.
Staged to:
http://go/dac-stage/reference/android/hardware/usb/UsbManager.html
Bug: 36672976
Test: make ds-docs
Change-Id: I9f1c202d0a6a6a5b25cf775e2b11119a26625bf1
Part of the redesign for P, designed to support multiple clients and
easier usage.
Bug: 67734082
Test: make from root
Change-Id: I1e12a0484350fabfc13af32269961ad0fc69f9b1
Per bug, these were mislabeled as broadcast actions, when they're
actually activity intents. This has consequences post-O, since
broadcast actions are now subject to limitations.
Doc is staged to:
http://go/dac-stage/reference/android/hardware/usb/UsbManager.html
Bug: 36672976
Test: make ds-docs
Change-Id: I2b515b1ac152de389f952af21166ed2ba7843044
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
