On nav bar 2/3 key mode and device landscape, the top task should
always opposite to nav bar, so top task location should be right
when seascape and left when landscape.
On gesture nav mode, because the nav bar always locate bottom so
keep it behavior.
Bug: 150990456
Test: Use each gesture mode and enter split mode then check it
Change-Id: Ia46f765c43c947350ee4970ea86aa9a0d707ad7d
ActivityStack#mTopActivityOccludesKeyguard may be
incorrectly updated by a non-top activity.
Bug: 149837574
Test: start emergency dialer from lockscreen
Change-Id: I830e572f008cbebb95f0d76416c70d948063dd97
This will be used by FlickerTests to capture composition state
in SurfaceFlinger trace.
Test: atest FlickerLibTest:LayersTraceMonitorTest
Fixes: 153563549
Change-Id: I3d09196ced43a1b0bac811e8f458c28be4e44992
Instead of using the map from atoms_info, we now receive uid information
in the form of StatsEvent annotations. The isUid annotation is exposed
from both LogEvent and FieldValue.
Test: bit statsd_test:*
Test: atest GtsStatsdHostTestCases
Bug: 150414601
Change-Id: Iebbe4ce5668de1ab91485daa1be9197cde6e8309
Bug: 153576019
Test: Checks if Maps will move into the ActivityView when Home is pressed (in AAOS)
Change-Id: I040bf008a2f41130d6f118f359c9cefffb5acfc4
When ApexManager switched from using ServiceManager.getService to using Binder.waitForService to retrieve apexservice, it lost the call to Binder.allowBlocking that was inside getService. Since ApexManager currently makes several synchronous binder calls, this call is needed to avoid Log.wtf()s.
Bug: 153360345
Test: atest ApexManagerTest
Change-Id: I6016477b20754a6dc0f31588bae4e679f08a1ba2
This is statically linked by the wifi service, so should be jar-jar'ed
out to a separate namespace to avoid other components in system_server
calling our copy of the stubs.
Bug: 151475926
Test: Device boots up and connects to wifi networks.
Change-Id: I79247b72a3b5f6dabf38c3cb9705fb5ca0aa729f
We've heard reports that some ContentProviders are sensitive to their
notifications being delayed, so this change adds a NOTIFY_NO_DELAY
flag that they can use to bypass any background delays.
Bug: 149370968
Test: none
Change-Id: I0465c8dee92cd5708c04035bc0396ce2d1083f67
When an app hasn't been used in a long time (long enough for it to have
naturally time out into the RESTRICTED bucket) and a prediction service
anticipates that an app will not be used anytime soon (by predicting the
app into the RARE bucket), then we drop the app into the RESTRICTED
bucket in such a way that the prediction service can bring it back out
at the appropriate time.
Bug: 153567783
Test: atest FrameworksServicesTests:AppIdleHistoryTests
Test: atest FrameworksServicesTests:AppStandbyControllerTests
Change-Id: I0ec846a6d1bc8e254cabe6a9b504f4cae071def8
Notification updates from system server always give us a new
Notification that has a new `when` field therefore we don't know when
the initial notification was posted.
Test: atest SystemUITests
Bug: 144324894
Change-Id: I2464e2ef924e3074227337ad7143694d7e283ec7
Add a warning that TelephonyManager methods may not behave
in a consistent way on devices that do not implement
FEATURE_TELEPHONY.
Methods may succeed, may fail loudly, may silently fail, depending
on underlying device support and manufacturer-specific decisions.
When FEATURE_TELEPHONY is not declared, CTS does not enforce any
particular behavior.
Bug: 150006590
Test: compilation (docstring-only change)
Change-Id: I80f5031a43ccc8e5af97d341cf00e48afb80f63a
Test: Manually, verified that service starts and that wall time is
shorter in traces.
Bug: 151331469
Change-Id: Idce6597c9b3fa0c72d65335bb44f854dbb677d5a
