Temporarily removing flag to avoid crash in bug linked while we figure
out a solution for this. More details on bug linked.
Test: 1. Settings > Security > Enable Screen pinning.
2. From overview > Tap on any app info > Select screen pinning
> Tap on home bar and observe logcat
3. Verify no crash
Bug: 149408635
Change-Id: Ieba081eae3f0cd66f99c54a2deb4e9653ec4cd9d
* Introduced new permission MANAGE_FACTORY_RESET_PROTECTION
which allows an application to set a factory reset
protection (FRP) policy.
* Added the new permission as the receiver permission when sending
a broadcast in setFactoryResetProtectionPolicy.
Bug: 148596703
Test: atest com.android.cts.devicepolicy.OrgOwnedProfileOwnerTest#testFactoryResetProtectionPolicy
atest com.android.cts.devicepolicy.MixedDeviceOwnerTest#testFactoryResetProtectionPolicy
Change-Id: I2a9c859c2304c12b58d7f16e6bae6dac15d3f8eb
The crash happens on the user long press volume key
3 seconds to trigger the accessibility service and pop up toast.
Bug: 142529032
Test: Manual test
Change-Id: I64b939b1efba772a5ea9ca55b00ee1e29ab26f37
After the discussion, shouldn't let developers use the general
string which is non resource id. And only support the resource id string.
Bug: 142532186
Test: manual test
Change-Id: I912effc500c72d2ac83cc344f4e4099f6f469652
At the moment classloader contexts are incorrectly computed in the
PackageManager for secondary dex files. There are two issues:
(1) The wrong computed classLoaderContext will be reported for a secondary
dex file if it was loaded at the same time as a primary dex file
- This is due to the continue statement that doesn't increment
dexPathIndex
(2) If a secondary dex file was loaded with a shared library then that
shared library info isn't passed through the dex load reporting
infrastructure, and thus its classloader context is incorrectly computed
in PackageManager.
In order to fix the issues described above & prevent further classloader
context computation divergences between the package manager and the
runtime, lets compute the classloader context in the runtime at dex load
time and report the expected classloader context directly to
DexLoadReporter (and thus the package manager).
Notes: This is mostly just a refactor (i.e. there are a lot of line
changes, but functionally speaking this set of CLs doesn't do much
except change where the classloader context is computed)
Addendum: The bugs described above could also be fixed by:
- changing DexLoadReporter to report information about shared libraries that
the reported classloaders depend on to PackageManager
- Teach DexoptUtils.processContextForDexLoad about shared libraries
- Fix dexPathIndex calculation in DexManager
I opted for this set of changes instead because this reduces the
possibility of context computation divergence between the framework and the
runtime. Additionally it feels more "solid" that the classloader context
is now computed directly when a dex file is loaded, rather than the
context recreated later on in the PackageManager.
Test: atest com.android.server.pm.dex.DexManagerTests
Test: atest com.android.server.pm.PackageManagerServiceTest
Test: Install app depending on shared library & uses secondary dex
files; adb shell pm bg-dexopt-job; launch app and see odex file
successfully loaded (from smaps/no logcat errors)
Bug: 148494302
Change-Id: I00357cfe086ff149f92c1078c6df6daa713c8f7c
Bug: 141165119
Test: atest CtsAutoFillServiceTestCases
Test: manual. Install sample app in bug and make sure app does not
crash and log error after applying the fix.
Change-Id: If61553126b694a0d520691a963f728cb46cb521d
As CE and DE data directory may not be ready when volume is mounted
(like a new volume). We try to mount data mirror after user data is
prepared. It will skip mounting data mirror if it's already mounted.
Bug: 149027213
Test: After reverting ag/10156695 and aosp/1218838, can see virtual disk
is mounted correctly in adb shell mount, and test app works and mounted
correctly after pm move-package.
Change-Id: If433914a93f7e6154f31715869f52b387157b2dd
- This CL use getMostRecentlyConnectedDevices() to get the
most recently disconnected devices.
- Register CachedBluetoothDevice.Callback to oberve the device
connection state used to update UI.
- Update UI when receive onRoutesRemoved().
- Add getMostRecentlyConnectedDevices() and
setMostRecentlyConnectedDevices() in ShadowBluetoothAdapter.java
- Add test case.
Bug: 149267220
Test: make -j42 RunSettingsLibRoboTests
Change-Id: I43660dc76cf5194cb24d83b5a17d4725fe750e6a
- Provide an abstract api named getScheduleInfoList.
- Implement a ScheduleInfo class.
Fixes: 148995400
Test: compilation
Change-Id: I236627daa478fb2d2d138a8832680b1ec2464b3b
Home stack was reordered to bottom after user switched. So, we
were able to navigate through all tasks by back key.
Position topmost task to top doesn't seem necessary, but had
unintentionally moved its parent to top.
Bug: 148087585
Test: switch user and go back
Change-Id: If0230a7ef5a118b442bea72e7a35defe9d4dea75
Activities could be remained at foreground when it has failures
in trial launch, which affects testing results of other apps.
Bug: 149326995
Test: atest google/perf/app-startup/hermetic-apps/cold-dropcache-test
Change-Id: Id364461ff5a97384590d1dc7cfb59cc8cf4e88a6
am skip reason: Change-Id I559d42089aeb09801d14c251c5165fca793c3cb3 with SHA-1 a1b805852e is in history
Change-Id: I312db6a0bd341833c53f83be3d72da5b1bf9d7cf
