Now that these methods are no longer called, and none of them are a
public API or have @UnsupportedAppUsage, they can be removed.
inCryptKeeperBounce() actually had one known app user via reflection,
despite the method not having @UnsupportedAppUsage. However, that user
only made the call if Build.VERSION.SDK_INT < VERSION_CODES.P, so it is
not being used anymore.
Bug: 208476087
Change-Id: Idc218e5f355bb61257b07cf5b5b6df5f4c6ece11
Also changes the SYSTEM_CHANGES notification channel to be IMPORTANCE_DEFAULT (by deprecating the existing, unused one).
Bug: 225373531
Test: manual by forcing the notification to show
Change-Id: I9743fe08cccbd8b6a9e7b367e32fe3e597b81ec4
Merged-In: I9743fe08cccbd8b6a9e7b367e32fe3e597b81ec4
* changes:
[automerge] Show check icon on current locale preference 2p: 286d948ebf 2p: 9f1bfe569a
[automerge] Show check icon on current locale preference 2p: 286d948ebf
Show check icon on current locale preference
Allows developers to set an empty locale in locale-config to disable
configuring the app's language
Bug: 224850207
Test: Manual
Change-Id: I8b06a61fb0e4ab253723850cf83d881d3e150638
Also changes the SYSTEM_CHANGES notification channel to be IMPORTANCE_DEFAULT (by deprecating the existing, unused one).
Bug: 225373531
Test: manual by forcing the notification to show
Change-Id: I9743fe08cccbd8b6a9e7b367e32fe3e597b81ec4
Migrate from ints to Strings so we can pass codenames. Otherwise we
can't use these attributes representing a release in progress until that
release is finalized. I.e. if release T is in progress, we don't get the
correct behaviour if we use "T" in those attributes.
Also added some more tests which found some edge cases that weren't
properly handled: tests for when the shared libraries are first removed
from bootclasspath and moved to a module and then added again to the
bootclasspath via a mainline update;
In turn those tests found a bug where we would apply the logic for
onBootclasspathBefore X on devices before X which is not required.
Bug: 191978330
Test: atest
com.android.server.pm.parsing.library.ApexSharedLibraryUpdaterTest
com.android.server.systemconfig.SystemConfigTest
Change-Id: I85a3287422877a95394153b575ae422745fda27d
Stop parsing the IKE options from the input IkeTunnelConnectionParams
if exists. The caller shuould get the relevant infortation the
params.
The field is also stored in the VpnProfile if it built from an
Ikev2VpnProfile.
Bug: 184750836
Test: atest FrameworksNetTests HostsideVpnTests
Test: build ; flash ; connect VPN successfully
Change-Id: Id05c17285915462c7a6cd51d5fb4ee5da7f465ba
The EROFS detection code is rather expensive. On Android 13 kernels we
can use a faster detection using /sys/fs/erofs.
Bug: 225092276
Test: erofs detected on android13-5.10
Change-Id: I0f1c2975f1de7810ee2334d2f09c9fa3722d0174
The helper methods provided by this class have been unused
since ag/13807667 (part of removing the old ChooserTargetService
functionality).
Test: http://cs/search?q=chooserutil&sq=package:android-internal
Bug: 148416928
Change-Id: I0aaaa5f597ef72097f1847a3187b335791287a60
In 12L, to support mulit-display devices, we changed the way to get the
status bar height by adding an API to calculate instead of directly
reading the resource of status_bar_height.
However, some apps still using Resources.getIdentify() to get this
internal resources dimen as status bar height to layout their UI which
cause status bar glitch in their app.
For compatibility purpose:
1. Create a new dimen res status_bar_height_default which will be used
by framework to determine the status bar heigth
2. For status_bar_height
- Set the value to the size which already consider the cutout size
for defualt display as before so that it won't breaking existing
app.
- It is only used for apps using Resources.getIdentifier()
Bug: 216782082
Test: verified on the apps with such issue.
Change-Id: I306efa187ffa69223c06fd248cfe57d183f96c59
This also adds the request id to the methods that hide the prompt to prevent stale requests from being handled. I wasn't able to reproduce the bug locally but it appears to be caused by these stale events.
Fix: 225275518
Bug: 213899762
Test: atest BiometricServiceTest AuthContainerViewTest
Change-Id: Iac414763dd0012e51b331abe649a50e353df5e1c
Clean up some leftover references and simplify
Add positive confirmation of flag changes via logcat
Change-Id: Id21b66953bb3b7c810e9d67809a673862a7ea821
Test: m -j update-api. Build and flash and test back behavior throughout
the system.
Bug: 227500290
Change-Id: Ibdb13d02e044741d05d99f1cad96e43dc0129fe4
