Also, allow "productivity_mode" config to be enabled via intent extra
as a developement aide.
Bug: 28006206
Change-Id: I7be8d96a0e924f9ce8023347e051d28d69a0eec9
RenderNode_Delegate nCreate now takes a reference to this. In the
Path_Delegate, the native_offset call with a destination path has been
removed.
Change-Id: I6332bb4733974b817e8a29eab82e2218fcf942c4
When the system is shutting down or the screen is going to be off, <Standby>
message will be broadcasted if and only if the setting variable,
Settings.Global#HDMI_CONTROL_AUTO_DEVICE_OFF_ENABLED, is enabled. This change
will make the shutdown case to be checked with the setting properly, too.
Bug: 27781559
Change-Id: Ia6605d6b5627ab1ff67285d72846b618a09548bc
Add shell commands to check on current FBE status and system ready
status. Mark variables without first-class locking as volatile.
Fix bug where UI automation would crash while device was locked by
marking it as forced direct-boot aware.
Bug: 26498834
Change-Id: Ib4dfb9350925e5413f93a09baacf84c62f2ba0ea
Reverting the revert.
The original CL(commit a666d74d4bc7e1298314c516d1309571fb87c212) had a
bug in it. It was calling accountExistsCacheLocked(), while holding
accounts.cacheLock. The function accountExistsCacheLocked, was in turn
calling into getUserAccounts, which acquires mUsers. And this causes
trouble. mUsers is a a lock on all accounts, and hence calling it after
holding accounts.cachelock is calling for trouble. Since the locks are
acquired in other order, it causes a potential deadlock issue, which we
discovered later on.
That bug was fixed by commit 0e592733ecbde2b7e7f2aa92001656dfbcae9641.
We already have useraccount object and should reuse it.
This reverts commit 27d0e1fd660a7e92644ab6a2893ac1149f0c0488. This
commit was unneeded as the bug had been fixed by that time.
Change-Id: I5328c31fd485fd2c1c652cd0e7c2c4bded38a5fd
Added handling of app query reponse from context hub.
Exposed the maximum message size to clients.
Change-Id: Ie96a860774d005ad6ad72acc88dc79964835486b
Since we switched this activity to draw the system bar backgrounds,
and clearing these flags leads to that we don't get the insets
communicated, we need to remove the clearing of the flags.
Bug: 27914346
Change-Id: I72114ac7cec40933fa45891b3d1441bd30f883d4
When the device was locked the fullscreen stack was laid out
fulllscreen, even though the configuration was half-screen, which
lead to a race between the app drawing and the unlock animation
so sometimes you could see the fullscreen frame when the unlock
animation started.
Instead, only layout in fullscreen if the docked stack is fully
"hidden".
Bug: 27154882
Change-Id: I4ba0c396eb0312c2bf2d911903b68c88d28aae8c
The current implementation makes the decision based on the
list of locales translated in frameworks/base
It will break if we remove country from the resource locale IDs
(e.g. fr-FR => fr)
It also offers no flexibility in case we want to suggest a country
based on other criteria.
Bug: 27378061
Change-Id: I3d8514e8abff83a4c98c5658533738611cf12576
The behavior of this command was not well specified in case of errors,
so it's better to remove it and let clients use 'list wifi-networks'
instead, checking for the value of the 'metered' column.
BUG: 27808364
Change-Id: I3f4216c143b4b2a803b99002585fafe0e3885665
Framework edition
When setting a user visibility hint on a fragment it was possible to
have a FragmentManager already set due to a transaction being composed
but before the commit, so only checking that we have one isn't
sufficient for determining whether we should perform a pending
deferred start. This could happen easily with ViewPager adapters. Use
isAdded() instead.
Also fix a bug where we could set our internal tracking of fragments
that need a deferred start incorrectly.
Bug 27814550
Change-Id: I3be65728650c48d27a3a9dd4ca15f52006d14ab9
- Between the time that the task view is bound and the thumbnail is
loaded, we should still draw the background color instead of nothing.
Bug: 27971061
Change-Id: I5b7a607b86a0da20fc6ca183b1d7bc4e9db9e377
