am: 0f6a6c4bc1
* commit '0f6a6c4bc15fee726ef9aeb0d99b1204767f431d':
Don't allow any app to specify rotation unless in home task
Change-Id: Id53a86c7c4878e90021d0d82172a1fbb49cc13fe
The previous logic was racy/buggy in a sense so that the non-home app
could still force the orientation when the divider was still minimized.
The logic is cleaned up so only the home task can force the orientation
in multi-window.
Change-Id: I9eccf86d9fa442375d6eca400cb6ac0815c9fa10
Fixes: 28675152
Rotation could change again after updateDisplayInfo is called. We
need to set stack bounds even for fullscreen stacks in this case.
Otherwise the bounds will be incorrect until it's rotated again.
bug: 28611814
Change-Id: I31289524a9ceacaaaa66924e9bf6cbe88fd83f99
am: 25018d41f4
* commit '25018d41f482fe21a45eb2e739f22dc7cc937428':
Fixed connectivity state in some power saving scenarios.
Change-Id: I7ebe3864657d2147034ffae400312e94deb5ef35
am: 3264b60738
* commit '3264b60738b0c8c611334d448aca4480eaffc1cc':
System server: Add Bluetooth to native processes
Change-Id: Ia2f3acf70364886cb4a088e716bf480550779cd8
If we're going to show metadata about a resolved implicit intent that
is targeted to a single package with multiple potential targets,
populate the ResolveInfo with the label and icon of the target
package's ApplicationInfo and set resolvePackageName. This helps use
cases such as EXTRA_INITIAL_INTENTS in ChooserActivity, where
sometimes apps set target packages but not components.
Bug 28739056
Change-Id: I8070d341fccc139463c5ac8d66db45fce02252e5
TelephonyRegistry should notify data status by correct subId,
otherwise in some case, SIM1 data status will be overried
by SIM2 data status.
Such as screen on/off action.If in fact SIM1 is data connected
to download something, but SIM2 is not,then sreen off,
both SIM1 and SIM2 will be notified to update data status.
Then SIM1 data status will be overried by SIM2 to be "no data
connected", before SIM1 data downloading is finished,SIM1
will not be able to show "data conneced" status.
Change-Id: Ia7d0767b3b4520294ee0d024903f7522cb0a0110
am: a285fdeb16
* commit 'a285fdeb160e822a2e1fe2fb6bd80ce91afcf181':
Fix a flicker when window is removed during entering animation
Change-Id: If69708ffa782088d9d50064a110d75ca2c81c066
am: 36d1296cf4
* commit '36d1296cf4f074599015b424161402f9b07da8ab':
Adjust divider when IME height is changed.
Change-Id: I2a4d8a16028350c6634ce5f11eca644019325ce1
- Always dim home stack and task fullscreen. The home stack could be
in split-screen mode, but we still want to dim dialogs that are
associated with the stack or task in fullscreen. The dialogs are not
really activities, but they are associated with the home stack for
things like dimming. Don't ask me why...
- Update the fullscreen dim layer bounds anytime the dim layer is
adjusted so we always have up-to-date bounds after rotation.
Bug: 28575624
Change-Id: I805c771153a2d25fb199bd9987bbf78a5967f6b9
When animation is started with saved surfaces, app may decide to
remove one of the child windows during early animation and replace
it with a new window. This causes the app below (usually Recents)
to show through for one or more frames.
If we started animation early with a window, delay removal of
that window until the app is allDrawn in the "traditional sense"
(i.e. allDrawn without using any saved surfaces).
bug: 28742353
Change-Id: I4ef663a947b737aae96c3ccfe13a9f4c1d0567f0
Previously, divider was adjusted for IME when IME window visibility is
changed. However, IME size can be changed without changing IME window
visibility. For example, when hardware keyboard key is pressed to show
emoji layout.
This CL checks if IME height has been changed and adjust divider position
properly.
Bug: 28389933
Change-Id: I9a561bd4796a0513c8b5c493884946883f160907
Do not post app token with the timeout message, instead put the token
in a list and post empty message only.
bug: 28744782
Change-Id: If809d8ee16bcc31067f25ae5696b62d09ea4b864
Add Bluetooth service to the interesting native processes to dump
during watchdog abort and ANRs. This may help if the process gets
wedged and cannot react normally to Java-side ANR dump requests.
Bug: 28658141
Change-Id: I788b7c299cc95748fdcddaa2be1d0e2d78f25ef1
am: b41088b4df
* commit 'b41088b4dfa8b077541cd3be69c51bd4bba4e938':
Pinner service for pinning files into memory
Change-Id: I6dc3f40dbbb5e327976f665de1451eb1d416ee2a
am: 2e35847a8f
* commit '2e35847a8f9557b59198fc053524eee0b965aab8':
fix filter for listeners that are not the rocket
Change-Id: I00092556795bb085060508cb18f62fbeecf42d09
Pin key files into memory to prevent having to fetch from flash
after boot. Improves system performance by preventing page cache
thrash. Retrieves files from a device-specific overlay to allow
specialization.
bug 28251566
Change-Id: I8532f52bd70271794dd7576976d13a524849ce7b
am: 562ea5ceb5
* commit '562ea5ceb5e10a3ea4dfd3825b2d639fbc6506b0':
Don't notify windows of resize during PIP animation.
Change-Id: Ib2c41bf5097755419ceb56aa62982ee5963d7316
NetworkPolicyManagerService (NPMS) manages 4 type of network restriction
when apps are running on background:
- Data Saver Mode (data usage restriction on metered-networks)
- Battery Saver Mode (power restriction on all networks)
- Doze Mode (power restriction on all networks)
- App Idle (power restriction on all networks)
These restrictions affects 2 parts of the system:
- Internal framework state on NPMS which is propagated to other internal
classes.
- External firewall rules (managed by netd).
Although each of the power-related restrictions have their own external firewall
rules, internally apps are whitelisted to them through the same
whitelist, and the current code is only updating the internal state (and
notifying the internal listeners) when Battery Saver Mode is on.
As a consequence of this problem, there are scenarios where an app
correctly does not have internet access (because the firewall rules are
properly set), but the NetworkInfo state returns the wrong state (like
CONNECTED / CONNECTED).
This CL fixes this problem by splitting the power-related logic from
updateRulesForRestrictBackgroundLocked() into its own
method (updateRulesForPowerRestrictionsLocked()), and making sure such
method is called whenever the firewall rules are updated.
Externally to this change, the CTS tests were also improved to verify
the apps get the proper connection state; it can be verified by running:
cts-tradefed run commandAndExit cts -m CtsHostsideNetworkTests \
-t com.android.cts.net.HostsideRestrictBackgroundNetworkTests
BUG: 28521946
Change-Id: Id5187eb7a59c549ef30e2b17627ae2d734afa789
We are notifying windows of resize as the frame moves (even though the
size does not change) during the pinned animation, confusing and
upsetting the client. We do want to notify it of the one resize
at the beginning or end of the animation, so we can't just block
reportResized on bounds animating. Luckily the other area that adds
windows to reportResized (Task) is smart enough to only do so if the
size has actually changed and not just movement, so we let those reports
go through and block ones initiating from here (which doesn't perform
a check that the size has actually changed).
Bug: 28559097
Change-Id: If1f983e7cc875175ce1d098c385478a9922dea67
