There is a key signing problem in general-tests so move all overlays
to device-tests.
Bug: 141998755
Bug: 153631240
Bug: 153630797
Test: atest InstallOverlayTests
Change-Id: Ic8274031c8bd0aca5a6b7ccfee53b047334ab060
KeyguardSliceView was being inflated by other tests. This caused real
controllers being created through Dagger. Replace views with mocks.
Bug: 153667872
Test: atest SystemUITests
Change-Id: I41b28bc886f97fab3fa8a0af63e743b07f4ec667
This exposes errors directly, which mirrors what PackageParser
used to do. Just a leftover TODO from the refactor.
Bug: 153472626
Test: manual install broken APK and check the error is logged
Change-Id: I06804ad7396196e28ce2177a671d4eef3958e1d6
Fixing a typo in the previous commit: s/remove/put/
Bug: 153013604
Test: ran CTS tests on sdk_gphone_x86
Change-Id: Iabe8ce51f38ac921aa5cc0e78b559e4a512b9273
This removes the dependency on re-delivery of sticky broadcasts by
having a single point in the system that listens to
RINGER_MODE_CHANGED_ACTION and RINGER_MODE_INTERNAL_CHANGED_ACTION.
Also, added some global mocks for Notification tests that were
constructing KeyguardUpdateMonitor (after many injections).
Also, added mock in KeyguardSecurityContainerTest.
Test: manual
Test: atest SystemUITests
Bug: 151641451
Change-Id: Ie81109cf1fe077bc4790f7a4e501df69dbb2323b
In quick switch flows, launcher will first swipe task snapshot
through recents animation, and then start new task with custom animation
options through startActivityFromRecents after gesture finish detected,
and then finish recents animation finally.
But that way user may experience flickering before the new task launch
and recents animation finish.
To improve quick switch flickering, we ignore the new task's custom
animation from recents and generate task remote animation target,
and then trigger a callback for launcher to control/animate this
task surface, more like a part of RecentsAnimation,
Also, adding removeTask method for launcher can flexibility remove the
new task animation target once no need to animate, so that launcher
can decide when to finish recents animation.
Bug: 152480470
Test: manual as below steps:
1) Doing quick switch task.
2) Make sure launcher can receive onTaskAppeared callback.
3) Make sure launcher calls removeTask successfully.
4) Make sure launcher can finish recents animation after 3).
Change-Id: I0692a280a49719229fa8871509bad37a1343a00f
If an application targets R+, prevent the application from being
installed if the app has a compressed resources.arsc or if the
resources.arsc is not aligned on a 4-byte boundary. Resources tables
that cannot be memory mapped have to be read into a buffer in RAM
and exert unnecessary memory pressure on the system.
Bug: 132742131
Test: manual (adding CTS tests)
Change-Id: Ieef764c87643863de24531fac12cc520fe6d90d0
There is no need for a content description on the associated icon, as
the title is sufficient.
Bug: 153288023
Bug: 153291530
Test: talkback
Change-Id: I8617151cbbbb24f437e93a7c106997ef355206b6
Request the IME to hide current inline suggestion on committing.
Bug: 149945531
Test: atest InlineLoginActivityTest
Test: atest InlineAugmentedLoginActivityTest
Change-Id: Ia19aebb7d84c6d858fa93ee51df1bbbf7d92eafe
Because of internal implementation of one way binder calls, in order to
unblock the boot phase, we need to put both the binder call and the
filedescriptor in the background thread.
Original boot time: 17758.6ms
New boot time: 17608.0ms
Bug: 130773130
Test: DeviceBootTest.DeviceBootTest#SuccessiveBootTest
Change-Id: Ib3524418a387c5902af8139e1b2aee82525b8e04
Fuzz testing cause out-of-memory errors
when passing very large port counts.
Now we check to make sure the port count is in a resonable range.
Bug: 135639926
Test: any MIDI test will exercise this code
Test: https://source.android.com/devices/audio/midi_test.html
Change-Id: Ic5dedc1eda86ff86a73a1da66ee6630c9662ceb8
These stubs contain the libcore sources inside them, so need not
compile against core_current.
Also rename the defaults rule to be in line with the new neverallow.
Bug: 144149403
Test: m
Change-Id: I5f1b01875b0073f942c692882db157a8c5788ce0
Merged-In: I5f1b01875b0073f942c692882db157a8c5788ce0
Looks like this is caused by calling removeView right before addView, which happens when we recreate the dismiss target. Sometimes, removeView has not completed by the time we addView again.
I wasn't able to reproduce the crash, but other places in sysui use removeViewImmediate for this purpose.
Bug: 153551432
Test: try rotating the screen a bunch with a PIP visible
Change-Id: Ic96173c1273b8476280a7daf63340bbe9613b21e
This patch uses Instrumentation parameter inside
getDefaultLauncher function to obtain user ID
from it and get default launcher namely for that
user as setDefaultLauncher function sets launcher
for the user from Instrumentation context. This
fixes incorrect launcher settings for the cases
that use two sequential calls to get/set
default launcher.
Bug: 145774461
Test: run cts -m CtsShortcutHostTestCases -t \
android.content.pm.cts.shortcuthost.ShortcutManagerMultiuserTest#testSecondaryUser
Signed-off-by: Sergii Iegorov <sergii.iegorov@globallogic.com>
Change-Id: I8941f5648ad783c7681fdb56677e855756db957d
Merged-in: I8941f5648ad783c7681fdb56677e855756db957d
* accountTypesWithManagementDisabled
* disableScreenCapture
For security logging nothing has to be done since the state is
stored in a system property, just changed it so that the logging
will be started after the migration and only events for the
right user are logged.
Also removed the todo about hardening for power cut case, the
risk of additional complexity sees to outweight the benefit.
Bug: 149075700
Test: atest DevicePolicyManagerServiceMigrationTest
Change-Id: I3a58325f2d6f415e51998c5096c5fc123d26602d
Instead of starting the sharesheet in the other profile when
choosing the "Switch to work"/"Switch to personal" button,
we now start the sharesheet in the same profile with the other tab
selected.
For example, we're in the personal profile and share something
via an app that uses its own sharing logic. That shows the
"Switch to work" button and when we press it, we now start
the sharesheet in the personal profile with the work tab selected.
The reason for this is to avoid user confusion when they go back
to the personal tab and it shows an empty state screen due to
lack of cross-profile intents.
Fixes: 152866292
Test: manual
Test: atest ChooserActivityTest
Test: atest ResolverActivityTest
Test: atest IntentForwarderActivityTest#launchInSameProfile_chooserIntent
Change-Id: Ic117c9c51c663b6574e7692022bac82f7c899ec2
