Adds setSustainedPerformanceMode(boolean) API for applications to set
the mode for a given window. The mode will be disabled automatically when the
window is no longer in focus.
Bug: 28150358
Change-Id: Ibe8bc564eeaaccbcaad5c4f792cda16da931dffd
Signed-off-by: Ruchi Kandoi <kandoiruchi@google.com>
am: 67288c5
* commit '67288c5b6f05e18e85dd9a520f273d311952276f':
Consolidate the HealthStats UI to only use milliseconds.
Change-Id: I8ea14a4502f124daee32c0ef92130200431f04e7
BatteryStats uses a mix of microseconds and milliseconds, and keeping
which one is which straight is difficult. The internal bookkeeping
is left using us where it already does, for the extra precision. But
having the API be mixed will only make it harder for developers, and
lead them to make the same mistake that I did in the API where I
missed some conversions.
Bug: 28197858
Change-Id: I99114bae259b9bdd47ce5c22e724d87bbd63336d
am: 6797d86
* commit '6797d86d76ee193bc20809f118163a86eaf28b4b':
Address API review for UserManager user creation
Change-Id: Ibfc33fcf16d958272b7dc6cad59e5ee557716706
Instead of calling out to external processes with a blocking IPC,
pass along a Binder on which the external process can pass back
the response. The calling process can then wait for the reply with
a timeout.
This eliminates watchdog restarts of the system_server when an external
process like telephony or bluetooth hangs.
Bug:26842468
Change-Id: I1b242e4ed22a63f1a4a0be8c78de8ac4d7bf56c5
Don't return null from createUserCreationIntent()
Provide a way for apps to query if the device
supports multiple users.
Some additional documentation for UserManager class to
make things clear about the types of users and relationship
with accounts.
Change-Id: I768d816e73a1d7f61cdc415f9e482adc79e2715a
Fixes: 28150359
Preparing and destroying users currently needs to be split across
installd, system_server, and vold, since no single party has all the
required SELinux permissions.
When preparing user directories on a storage device, always enforce
the serial number and destroy data if we run into a mismatch. When
deleting a user, write the updated user list first before we start
destroying data. Also start reconciling users on internal storage
at boot, so we can recover from stale data left behind from partially
destroyed users.
Check both CE and DE user directories when reconciling user storage
on a newly mounted storage device.
Bug: 27896918
Change-Id: I4536c82b0196e2720628c4f73fccb742c233350b
am: f1320d1
* commit 'f1320d1d7fb91b66e82533ea6b93ffd6903d834e':
Maybe decrypt user when quiet mode is disabled
Change-Id: I5f021888ad89e554f8b47e9ff8283f2b12bdabee
When quiet mode is disabled for a user and that user is not currently
decrypted, we show a confirm credentials screen to trigger decryption
of that user. Only if that was successful, do we actually disable quiet
mode.
Bug: 27764124
Change-Id: Ib1f649194d89e225dad62c14f3ddba1fa3d79da2
Previously many usages of UserManager.getProfiles and getEnabledProfiles
were only using ids of returned users. Given that the list of users needs
to be parceled and unparceled for Binder calls, returning array of ids
minimizes memory usage and serialization time.
A new method getProfileIds was introduced which returns an array of userIds.
Existing method calls were updated where appropriate.
Bug: 27705805
Change-Id: Ic5d5decd77567ba0f749e48837a2c6fa10e812c0
am: 0f74260
* commit '0f7426090aead6b5ea93ee612619d5a7855b1f4f':
Revert "Remove old FUSE bypass now that we have sdcardfs."
Change-Id: I467f76250bc684d92bed030d22314d1f637464db
am: 16e0976
* commit '16e0976152ff8cd6eb5cffd5f723f4bb6c220fd4':
Give users and devices control over sdcardfs.
Change-Id: Ic311b3bf56f5e9417f9785dab25cbbd7ea148c30
Instead of relying only on kernel support for sdcardfs, give each
device the ability to quickly toggle between sdcardfs and FUSE. Also
add the ability to users to explicitly enable/disable the behavior
for testing and debugging purposes.
Bug: 27991427
Change-Id: Ia57f12f6ead888ab85101004bdd8c8003537b116
There are a handful of looper threads in the system_process that
are shared by dozens of different internal services. To help track
down what these operations are, tag the processing of each message
with a string that tries describing where it originated from: the
class name of the Handler, and the message number or class name of the
Runnable.
Bug: 28046299
Change-Id: I409ec43fea8daaae4fd70df05d4fed929a7249ae
am: edd2e60
* commit 'edd2e60ae343d15304415489ee752527220b5ac1':
Remove old FUSE bypass now that we have sdcardfs.
Change-Id: Ibd1a63bd1f8ce72ea650bbd0a972314e90e3f7af
This forces everyone to go through sdcardfs, instead of letting them
around the back door.
Bug: 27992761
Change-Id: If1d4d5daa4b32bb3be7de10102bab24d63552b65