See b/323650746 and b/323649900 for issues that should’ve been caught by pre-submit.
Bug: 323649900
Bug: 323650746
Change-Id: I77d664b6fce6a3f76a4c9a6b39202f6e9d47da33
Test: atest SettingsUnitTests
When the user goes through the flow of removing the device's lockscreen
knowledge factor (LSKF), warn them in case they have apps with
auth-bound keys on the device. Auth-bound keys that are bound to the
LSKF's secure user ID (that is, auth-bound keys that can be
authenticated by the user entering their LSKF) will be invalidated
when the LSKF is removed.
That means apps will not be able to decrypt the data encrypted with
these keys or use them to sign anything anymore (potentially effectively
losing the user's ability to prove their identity).
In this case, change the warning message that is shown to the user,
to make it clear wallet apps (that typically use such keys) will stop
working as well as other apps.
Bug: 302109605
Test: Manual, enrolled a PIN, face and fingerprint and tried removing PIN.
A CtsVerifier test will be added later.
Change-Id: I276b744f54763e291abe1f20824da4f8f156679d
Currently, the stylus hover icon can only be shown when
config_enableStylusPointerIcon is set to true. This means that the
users do not have a choice of turning the feature on or off.
This CL introduces the capability to do the same. This CL adds the
toggle in the StylusDevicesController to be shown when stylus is
connected. The toggle is mapped to the STYLUS_POINTER_ENABLED secure
setting which InputManagerService listens to turn on and off the stylus
pointer icon.
Test: manual
Steps:
1. Change the value of config_enableStylusPointerIcon as true.
2. Build the images and flash it to a stylus supporting device.
3. After the device is booted, hover over the screen, the stylus
pointer should appear.
4. Go to Settings > Connected Devices > Stylus and tap on
"Show pointer while hovering" toggle.
5. Try hovering over the screen, check no pointer icon is shown
6. Repeat Step#4, check that stylus pointer appears.
Run
- make RunSettingsRoboTests \
ROBOTEST_FILTER=StylusDevicesControllerTest
- atest SettingsProviderTest
Change-Id: Idfff9b4307370cc510a5f94bd57777c30c96e854
When physical keyboard is connected, on enter press accept the new name
and dismiss the dialog.
Bug: 319621722
Test: atest BluetoothNameDialogFragmentTest
Flag: NA
Change-Id: Ibc4812ad559d65eb97156d83d2a6124893ffd3a6
With the Tile fulfillment avialable now this change reverts the interim
strings added for hide behaviour.
Also change the strings based on latest mocks.
Screenshot : go/ss/BCCEknnFyuJnzAq.png
Bug: 309950257
Test: Verified manually
Change-Id: Ia27a9a8b32883e0821531840b3644a79b2d18d17
The device might still in advertising mode even if it's bonded. We can
just ignore this kind of devices in the scanning result.
Bug: 307890347
Test: manual test
Change-Id: I782cc62edd4fec779f5f55444425b32a77f85e5e
Checks the gatt status in `onConnectionStateChange()` and `onServiceDiscovered()` callbacks. Disconnects and removes the gatt from the `mConnectingGattList` if the gatt status is not success in these callbacks.
Bug: 307890347
Test: manual test
Change-Id: Iab09f13b2ff3d33e5c4d6a8710736307c26b17e7
- Revert "Cleanup smart battery entries (1/3)" patch only instead whole topic, updated part of codes to resolve the conflicts
This reverts commit 742e506d13.
Reason for revert: b/315401539
Bug: 315401539
Change-Id: I75a4e4f75b624c90aae18288c77214c0238e43eb
The test doesn't need to mock fragment at all, just need to pass in a fragment without activity.
Bug: 314929422
Test: atest
Change-Id: I9fb2f38c9c00109dd0d74c8f1e0d405022f634e3
These three strings are updated to match
the latest figma mocks:
https://screenshot.googleplex.com/6JvDwmhKh3ANTzR
Other strings like the summary text will
be done in a follow up.
Test: on device
Bug: 322074376
Change-Id: I70b7a5317056abc669d581d11ba2b93dad2adba4
