summaryrefslogtreecommitdiff
path: root/core/java/android/hardware
Commit message (Collapse)AuthorAgeFilesLines
* Fix settings activity showing background bp whenHao Dong2025-07-082-0/+34
| | | | | | | | | | | | | | | | | | | | createConfirmDeviceCredentialIntent() API is used. If the app uses createConfirmDeviceCredentialIntent(), ConfirmDeviceCredentialActivity is the top activity which has "settings" as package name. Then if the app switches to settings, since previous foreground check only checks package name, biometric prompt isn't cancelled. This CL adds a class name check for this case. Flag: EXEMPT bugfix Bug: 339532378 Test: manual test with sample app on emulator Test: atest BiometricActivityTests#testConfirmDeviceCredentialActivityDismiss_whenSwitchToSettings (cherry picked from https://googleplex-android-review.googlesource.com/q/commit:b363da50d853018536fae5d214340a9bd7f2639b) Merged-In: I722e285cd15869799b9fadd2324014cf3c6d44ad Change-Id: I722e285cd15869799b9fadd2324014cf3c6d44ad Change-Id: Ib6b6d28effd418667121ec821576e2799b9dd969
* Use type safe API of readParcelableArraykumarashishg2023-11-101-1/+2
| | | | | | | | | | | Bug: 291299076 Test: Build and flash the device and check if it throws exception for non UsbInterface object Test: atest CtsUsbManagerTestCases (cherry picked from https://googleplex-android-review.googlesource.com/q/commit:85d7e6712a9eeeed3bdd68ea3c3862c7e88bfe70) (cherry picked from https://googleplex-android-review.googlesource.com/q/commit:8c55c8ca3f3646ba15e5f4bda4e28f713860e3f0) Merged-In: I2917c8331b6d56caaa9a6479bcd9a2d089f5f503 Change-Id: I2917c8331b6d56caaa9a6479bcd9a2d089f5f503
* Merge tag 'android-13.0.0_r52' of ↵George Zacharia2023-08-0213-79/+154
|\ | | | | | | | | | | | | https://android.googlesource.com/platform/frameworks/base into t13.0 Android 13.0.0 Release 52 (TQ3A.230605.012) Change-Id: Ic80f318636f1f70bbd009504352ddde511d0dead
| * DO NOT MERGE Force slowJpegMode on certain camera1 appsChengfei Tao2023-03-221-7/+17
| | | | | | | | | | | | | | | | | | | | Turn off the large JPEG stream on camera1 apps that experience high power consumption during video call Bug: 254350466 Test: Manual testing with Messenger app video call Change-Id: Ia5a96160f605f14d159412cd71f49791c1cfbd86
| * Merge "Adding boolean to determine whether a surface is MultiResolution" ↵Scott Wiest2023-03-213-1/+5
| |\ | | | | | | | | | into tm-qpr-dev
| | * Adding boolean to determine whether a surface is MultiResolutionScott Wiest2023-03-203-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | Test: Ran through CTS Camera Extensions test cases Bug: 274035443 Change-Id: I07b4a7eb14ea7452f27eb4f4480585df730ba7cd
| * | Add display committed state to DisplayInfoNicolo' Mazzucato2023-03-141-1/+26
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds the committed state to the display. The `state` is used to set the correct power state (e.g. turning display on/off), however there was no way to know when this power state change finished. This new "committedState" aims to fulfill this gap. DisplayListeners receives a `onDisplayChanged` callback whenever the power state change is fully committed, and can get this information from DisplayInfo. This will be used in a follow up cl to improve unfold latency performances. Bug: 223808403 Bug: 220690092 Bug: 197515205 Bug: 273204503 Test: atest LocalDisplayAdapterTest && manual Change-Id: Ia2fbab768b696c59578d974c88157ee3c8f3ddde Merged-In: Ia2fbab768b696c59578d974c88157ee3c8f3ddde (cherry picked from commit 07c6ebdd97ea3e9e3640fa5165b24249a52dd7e5)
| * CameraManager: Swap propertyName / packageName in call to getProperty()Austin Borger2023-03-091-2/+2
| | | | | | | | | | | | | | | | propertyName should be the first argument, not packageName. Bug: 272595790 Test: Added manifest property to sample app, trying all combinations Change-Id: Ida07d367a265f1bd703461dfbedc08f6cdeaba50
| * Merge "Camera: document multiResolution raw behavior" into tm-dev am: ↵Shuzhen Wang2023-02-242-20/+21
| |\ | | | | | | | | | | | | | | | | | | | | | | | | b9aa94e390 am: a09cc401fe Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/21548857 Change-Id: Ic41ce8e7634090cbfdc6650f0ee558583fbfdbbc Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
| | * Merge "Camera: document multiResolution raw behavior" into tm-dev am: b9aa94e390Shuzhen Wang2023-02-242-20/+21
| | |\ | | | | | | | | | | | | | | | | | | | | | | | | Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/21548857 Change-Id: If5c8e2bbed3b763dafd0316cbb3064559c2c3424 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
| | | * Camera: document multiResolution raw behaviorShuzhen Wang2023-02-232-20/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Document that mutiResolution RAW can be supported for a logical camera without RAW capability. Test: Build Bug: 269221911 Change-Id: I24269dd63c6f354a53c39de513a140907a0e41d2 Merged-In: I24269dd63c6f354a53c39de513a140907a0e41d2
| * | | RESTRICT AUTOMERGE adding new refresh rate priorityOleg Petsjonkin2023-02-021-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | new priority for auth screen. this allow to request higher refresh rate for screens where auth possible, and avoid swithcing rate when LHBM mode is activated Test: atest DisplayModeDirectorTest Bug: b/263908377 Change-Id: I2c19941dd9507d7e9171e30f6f433384ef620a92
| * | | Merge "RESTRICT AUTOMERGE Camera: Fix missing onPhysicalCameraUnavailable" ↵Michelle Ho2023-02-011-0/+9
| |\ \ \ | | | | | | | | | | | | | | | into tm-qpr-dev
| | * | | RESTRICT AUTOMERGE Camera: Fix missing onPhysicalCameraUnavailableMichelle Ho2023-01-181-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When onCameraAvailable invoked for a logical multi-camera, all of the physical cameras of a logical multi-camera are default available (i.e., no onPhysicalCameraAvailable would be called). So if some specific physical cameras are unavailable, onPhysicalCameraUnavailable should be invoked after onCameraAvailable. Bug: 262979670 Test: atest CameraManagerTest Change-Id: I77d32cd1d1c5a6c63950961724af7b41f8cdf1e6
| * | | | Merge "Camera: Fix physical camera availability update" into tm-qpr-devMichelle Ho2023-02-011-3/+8
| |\ \ \ \
| | * | | | Camera: Fix physical camera availability updateMichelle Ho2023-01-181-3/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We should always update the physical devices availability record once physical camera status changed, or the applications cannot receive the status change callbacks correctly. Bug: 262979670 Test: atest CameraManagerTest Change-Id: I0b0238612bce593d6722bec79908fe046d6d3e84
| * | | | | Camera: Remove 3 processed streams from streamUseCase combinations am: ↵Shuzhen Wang2023-01-281-2/+2
| |\ \ \ \ \ | | | |_|/ / | | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6ddf341bde am: d01df7fec4 Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/21085008 Change-Id: Ief49906f013a810f31a29881b8253d035b8423a8 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
| | * | | | Camera: Remove 3 processed streams from streamUseCase combinations am: ↵Shuzhen Wang2023-01-281-2/+2
| | |\ \ \ \ | | | | |_|/ | | | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6ddf341bde Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/21085008 Change-Id: Ib54e83c95f5453dea9254685036a7d61d08db354 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
| | | * | | Camera: Remove 3 processed streams from streamUseCase combinationsShuzhen Wang2023-01-251-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For LIMITED device level, the maximum number of processed streams is 2. To make the stream use case mandatory combinations consistent with LIMITED device level, remove the mandatory combinations with 3 processed streams. This is a doc update only. Test: Build and read doc Bug: 266436267 Change-Id: I83aa6858bb80056dc78d7eeadd0083f8e8caf2e9
| * | | | | Merge "Camera: Remove 3 processed streams combination for stream use case" ↵Shuzhen Wang2023-01-281-24/+0
| |\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | into tm-qpr-dev
| | * | | | | Camera: Remove 3 processed streams combination for stream use caseShuzhen Wang2023-01-231-24/+0
| | | |_|_|/ | | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For LIMITED device level, the maximum number of processed streams is 2. To make the stream use case mandatory combinations consistent with LIMITED device level, remove the mandatory combinations with 3 processed streams. Test: vendor testing, Camera CTS Bug: 266436267 Change-Id: I4ba19813050e70c7f247847fb9579f57fb31d160
| * / | | | docs: Updating obsolete "Key Character Map" linkAndrew Solovay2023-01-201-1/+1
| |/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The target page moved a couple of times and it looks like there wasn't a redirect set up. Verified that https://source.android.com/docs/core/interaction/input/key-character-map-files currently works. Change-Id: Ia3ea39ec7c2fd99c46bb7194790c999e1d9a35c4 Fixes: 224379018 Test: m -j 8 ds-docs-switched
| * | | | Merge "Camera: Clarify doc for registerAvailabilityCallback" into tm-dev am: ↵TreeHugger Robot2023-01-161-0/+17
| |\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 837979c612 am: efa05a9926 Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/20919943 Change-Id: Ic29685e1507ce661bfdf1cd842e64ab9d24a0710 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
| | * | | Merge "Camera: Clarify doc for registerAvailabilityCallback" into tm-dev am: ↵TreeHugger Robot2023-01-111-0/+17
| | |\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 837979c612 Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/20919943 Change-Id: I533a399481b4a2f9d9931c46fa3588cccaf6b638 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
| | | * | Camera: Clarify doc for registerAvailabilityCallbackShuzhen Wang2023-01-101-0/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Camera availability callbacks's order matter. If the application runs the callbacks on an executor, and the executor is implemented using multiple threads, the order of the callbacks may change. Test: Build and read docs Bug: 263235259 Change-Id: I88913215e0545a096958aaba6b7b2b7d73a4f0a0
| * | | | Merge "RESTRICT AUTOMERGE Revert "Camera: Fix missing ↵TreeHugger Robot2023-01-161-9/+0
| |\ \ \ \ | | |_|_|/ | |/| | | | | | | | onPhysicalCameraUnavailable"" into tm-qpr-dev
| | * | | RESTRICT AUTOMERGE Revert "Camera: Fix missing onPhysicalCameraUnavailable"Michelle Ho2023-01-131-9/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit 08c0efb03a4e648e6a5fc5de13bc9678d384e106. Reason for revert: GCA incompatible, need to submit along with b/263549589 Change-Id: I16501fab74e154aca97bd687340118e11c3200bf Bug: 265424740
| * | | | Merge "Camera: Fix missing onPhysicalCameraUnavailable" into tm-qpr-devMichelle Ho2023-01-121-0/+9
| |\| | |
| | * | | Camera: Fix missing onPhysicalCameraUnavailableMichelle Ho2023-01-111-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When onCameraAvailable invoked for a logical multi-camera, all of the physical cameras of a logical multi-camera are default available (i.e., no onPhysicalCameraAvailable would be called). So if some specific physical cameras are unavailable, onPhysicalCameraUnavailable should be invoked after onCameraAvailable. Bug: 262979670 Test: atest CameraManagerTest Change-Id: I6ee199ba30fa6f8c44c65d1e1d173fe6fd9ec3fe
| * | | | Merge "CameraDeviceImpl: Follow through reporting device errors even if the ↵Austin Borger2023-01-111-2/+5
| |\ \ \ \ | | | | | | | | | | | | | | | | | | remote device was never initialized." into tm-qpr-dev
| | * | | | CameraDeviceImpl: Follow through reporting device errors even if the remote ↵Austin Borger2023-01-101-2/+5
| | |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | device was never initialized. It's possible for setRemoteDevice to be called *after* libcameraservice calls onDeviceError. It would be risky to implement changes to ensure setRemoteDevice gets called first , so use a simple boolean flag to track whether the remote device was initialized. If it wasn't, then we can't assume the user isn't interested in device errors - that is only true if the device was closed. Bug: 263429133 Test: Ran CtsCameraTestCases on cuttlefish Test: StreamedAppBehaviorTest#appsInVirtualDevice_shouldNotHaveAccessToCamera Change-Id: Id1990dcb17e5ec2afc562bf76e410b58a49dcf77 Merged-In: Id1990dcb17e5ec2afc562bf76e410b58a49dcf77 (cherry picked from commit 2a95ec27a18eb3526a4c279bcc283e6d7e17c593)
| * | | | Merge "Per-app compat treatment for overrideToPortrait." into tm-qpr-devAustin Borger2023-01-112-19/+34
| |\ \ \ \
| | * | | | Per-app compat treatment for overrideToPortrait.Austin Borger2023-01-092-19/+34
| | |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Camera framework consumers will have the option to opt in or out to the rotate and crop fix for foldables via a manifest property. This will allow apps which correctly handle the landscape sensor to obtain the full FOV of the camera. Test: Tested opt-out in Camera2Basic sample, opt-in in CTSVerifier. Bug: 263965273 Change-Id: I190963c4f8dfba29dab7570397c33f44cab702e3 Merged-in: I190963c4f8dfba29dab7570397c33f44cab702e3
| * / / / Skip falsing on unfolded devices.Dave Mankoff2023-01-111-0/+9
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Exposes the already-known folded state on FoldStateListener such that it can be queried when needed. Bug: 236197248 Test: manually on a foldable && atest SystemUITests Change-Id: I1bca6254b7e8528e0a999d8f171e0ee1f966aeb4
* | | | Merge tag 'android-13.0.0_r49' into t13.0Semavi Ulusoy2023-05-171-0/+10
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | Android 13.0.0 Release 49 (TQ2B.230505.005.A1) Change-Id: I562410c4cae2550692078d7e7545392152b31b1c
| * | | | RESTRICT AUTOMERGE adding new refresh rate priorityOleg Petsjonkin2023-02-171-0/+10
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | new priority for auth screen. this allow to request higher refresh rate for screens where auth possible, and avoid swithcing rate when LHBM mode is activated Test: atest DisplayModeDirectorTest Bug: b/263908377 Change-Id: I2c19941dd9507d7e9171e30f6f433384ef620a92 (cherry picked from commit 67b1c6b1c29b1c19782bb29f56495067d75656a9) Merged-In: I2c19941dd9507d7e9171e30f6f433384ef620a92
* | | | Add missing Nullable annotations to UsbDeviceConnection.controlTransfer.Mateus Azis2023-05-051-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The Javadoc already states that 'buffer' can be null. Test: N/A, no functional change. Google: 2383855 Change-Id: I55634f58a7f2aa4f6c0b8157798e2ade27cf75dc
* | | | Revert "UsbManager: enableUsbDataSignal: return early if HAL version is too old"Semavi Ulusoy2023-04-231-9/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit f8e6ceee83e1553b6d7856d32841f8eb57f48c93. reason: abandoned on LoS: https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/343791 Change-Id: I2ee788b59a717e78274574e9ac075308bafc1891
* | | | Merge tag 'android-13.0.0_r35' of ↵George Zacharia2023-04-0318-562/+1067
|\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | https://android.googlesource.com/platform/frameworks/base into t13.0 Android 13.0.0 release 35 Change-Id: I709958b2f015d1774b2ece25894467c3a279f93c
| * | | Merge "Camera: Enable override to portrait by default" into tm-qpr-devEino-Ville Talvala (Eddy)2022-12-201-1/+1
| |\ \ \
| | * | | Camera: Enable override to portrait by defaultEmilian Peev2022-12-191-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Enable 'OVERRIDE_FRONT_CAMERA_APP_COMPAT' for all target SDK versions. Bug: 250678880 Test: Manual using test apps Change-Id: Ie334b86ef0c2bc3c79a797d01d3e4f3fc770f82d
| * | | | Merge "Allow non-IPC processes to setStylusEverUsed in InputManager" into ↵Vania Januar2022-12-201-6/+0
| |\ \ \ \ | | | | | | | | | | | | | | | | | | tm-qpr-dev
| | * | | | Allow non-IPC processes to setStylusEverUsed in InputManagerVania Januar2022-12-191-6/+0
| | |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | Bug: 253013763 Test: atest StylusListenerTest Change-Id: Ib9bc1c4a613c1b1a79cd7e37c5c0593a0313273f
| * | | | Merge "Make DPC listen to auto-brightness mode changes" into tm-qpr-devPiotr Wilczyński2022-12-151-7/+0
| |\ \ \ \ | | |/ / / | |/| | |
| | * | | Make DPC listen to auto-brightness mode changesPiotr Wilczyński2022-12-141-7/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - remove brightness mode code from PowerManager Bug: 161868123 Test: Make sure that switching auto-brightness mode still works correctly. Test: atest PowerGroupTest Test: atest PowerManagerServiceTest Change-Id: Ie8bed709c14a715d2f834eb4404463727f4dab13 Merged-In: Ie8bed709c14a715d2f834eb4404463727f4dab13
| * | | | DO NOT MERGE CameraManager: Enable override to portrait by default for ↵Austin Borger2022-12-131-2/+2
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | devices with the system property turned on. Bug: 250678880 Test: Checked app behavior on affected device. Change-Id: If3dcd001f9f393c2fd153aadda116302456df10b
| * | | Merge "DO NOT MERGE CameraManager: Provide flag for overriding camera output ↵Austin Borger2022-12-092-8/+59
| |\ \ \ | | | | | | | | | | | | | | | to portrait." into tm-qpr-dev
| | * | | DO NOT MERGE CameraManager: Provide flag for overriding camera output to ↵Austin Borger2022-12-052-8/+59
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | portrait. Apps commonly do not handle landscape orientation cameras correctly. In order to prevent stretching and rotation issues in these apps, this patch adds a flag to override the behavior of these landscape cameras to produce a portrait image instead by changing the SENSOR_ORIENTATION reported by CameraCharacteristics and applying a 90 degree rotate and crop. It also adds a CompatChanges entry which will track which apps require this treatment. Test: Ran on foldable device with several camera apps to verify behavior. Bug: 250678880 Change-Id: I92b6f227916b97828ab6a7f856eea5a1e427644d
| * | | | Allow pickupGestureEnabled default configurableBeverly2022-12-071-1/+5
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | Overlays can override the default enabled behavior. Fixes: 256185823 Test: manual Change-Id: I57f5f80647f52a9006fcaa66252c096f9883c7ba
| * | | Do not send updates for disabled displays.Santos Cordon2022-12-023-7/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If a display is disabled, do not share it outside of DisplayManagerService. This will help by not creating any unnecessary updates for displays that are disabled, and also not informing Applications of displays that they are unable to use. Also fixing a concurrency issue with DMS.handleLogicalDisplaySwapped which became apparent with this CL. Deferring the runnable with a Handler.post() caused the display-state-OFF update to happen after a newer change to turn the display ON. This caused the device to startup into a black screen. Removed the unnecessary call (since the displays are now made to both go into the "transition" state) to update the state and removed a lot of the redundant code with handleLogicalDisplayChange() which was called at the end of the method anyway. Bug: 221071695 Test: atest com.server.android.display Test: Manually verify display layouts still successfully change, and also confirm logs no longer hand excessive add/remove display notifications. Change-Id: I003fd91567630a447cf030b6fb83e5cb1041bcb5 Merged-In: I003fd91567630a447cf030b6fb83e5cb1041bcb5
generated by cgit v1.2.3 (git 2.25.1) at 2025-12-21 01:51:38 +0000