Bug: 186868020
Test: service started successfully
Change-Id: I4f152db83ba39e3ff39d4a4706fcfa7c2ab9d89c
(cherry picked from commit 5f95bba46592adef642742dff2a22687d4cd2c88)
For apex-system-services, we allow them to be explicitly started in
SystemService if there is a dependency on them from the rest of the
framework during dessert development. We also need to preserve their
manifest declaration for any previously launched dessert releases.
To avoid starting the same service multiple times, keep track of which
services have been started in SystemServiceManager and ignore
duplicates.
See go/updatable-system-services#bookmark=id.dnv20ia7siqd for more
details.
Bug: 192880996
Test: presubmit
Change-Id: I0a9e48eac9fd5739e2c35818fa483a8e479c13a1
NetworkStatsService is using INetworkManagementService APIs, which
cannot be accessed after moving into the mainline module. So, replace
and remove those hidden API usages.
Bug: 209738761
Test: atest NetworkStatsServiceTest
Change-Id: I5740f6d8a54e9a06c6dbb93203cb4c954383c3c8
Apex services must be the last category of services to start. No other
service must be starting after this point. This is to prevent
unnecessary stability issues when these apexes are updated outside of
OTA; and to avoid breaking dependencies from system into apexes.
Bug: 192880996
Test: presubmit
Change-Id: I42a5a1745c7fc0784fa2fef554c3d6439fd4c7fb
The initial selection toolbar related architecture. Render service
part and the implementation will be revised in the follow up changes.
Bug: 190030331
Bug: 205822301
Test: manual. Can boot to home and get manager successfully.
Ignore-AOSP-First: new file for T
Change-Id: Iab5d5f2e5e48e6258a63fb0c479194c958ea61e8
- Split out nsd APIs and hidden APIs to Connectivity module.
- Keep the all files in f/b/packages/Connectivity-T and add
framework-connectivity-tiramisu library on p/m/Connectivity.
Then make framework to use this module library.
- Remove NsdService from SystemServer which will register from
ConnectivityServiceInitializer
Bug: 206893064
Test: m online-sdk-dev-docs
Test: atest FrameworksNetTests CtsNetTestCases
CTS-Coverage-Bug: 207804007
Change-Id: I72c7de124b9cc53f2263bd452ecd5f39e88e485b
This implements a basic version of go/angel-in-mainline-api, only
for the bits that are unlikely to change (i.e. introduce the ability
for safety sources to provide data to the safety center).
SELinux Policy changes in aosp/1897505 and aosp/1899011
Test: ag/16284943
Ignore-AOSP-First: Yes
Bug: 203098016
Bug: 203400898
Bug: 205111656
Change-Id: I5d139782decf5226f0c4a8dcaed7c5691a86fed4
Design doc is at go/statsd-bootstrap-logging. Creates a proxy service for
logging atoms from bootstrap processes to statsd. Service has one API,
which converts StatsBootstrapAtom into StatsEvent and logs to statsd.
This should only used by processes that start in the bootstrap namespace
and cannot directly link statsd's libraries to log to statsd.
Bug: 204889815
Test: booted, made sure binder service was published.
Change-Id: I09709a30a42a7a398234c995324f62a0d62ad24f
Create a skeleton system service which will be used to run Isolated
Compilation using a system server classpath fragment in the CompOS
APEX.
This has no effect if the CompOS APEX is not present (i.e. isolated
compilation is not enabled).
Bug: 199147668
Test: starts up with CompOS present & not
Change-Id: I5ee853cfaf4d9633dd8db348d13e0dfe00bd4dca
this service is required for screen recording to work. Specificially
for WearMediaScreenRecorder to start recording the screen.
BUG: 171561784
Test: N/A (manually check that service has been launched)
Change-Id: I38ecc94d68bf7c0c48a3d57138cf1da4ad890064
(cherry picked from commit fd7a0e8fc1bc1be717f084aec1ef89dc1e67847e)
The following services are disabled for watches
* TwilightService - there is no night mode equivalent in Wear
* WiredAccessoryManager - watches have no wired inputs
Bug: 132729373
Change-Id: Ib118532931334528527f8a29bd0cd47639eecf95
Signed-off-by: Julius D'souza <jdsouza@google.com>
(cherry picked from commit 94cbb8e821f8ad8031b936d7feb95f85954722c7)
(cherry picked from commit 3b7f73a984e301d6574e800bbf069e507cf0319f)
- APIs the get the current process name
- APIs to get the process start "request" time
Fix: 205629074
Fix: 205337677
Test: atest CtsProcessTest
Change-Id: Id284fa169eb303011cdade6c3ab96e7026654612
Calls the SupplementalProcessFrameworkInitializer to
register the supplemental process service. This service
is started from SystemServer.
Test: Manual. Check logcat to ensure service has started
Bug: 204989700
Change-Id: Iaafb45fcc0d0be2c15bb6a6206114d59fe4bbf17
Execute the on start user lifecycle phase in parallel.
Services will be a added to a new thread pool, and depending
on which category they are in, they will either be executed
right away (bootstrap and core categories), or run in parallel
along with other services in that category (other category).
This change will only apply for non-system users for now.
Additionally, low ram devices will have this change disabled.
Initial results show about 16% improvement in execution times.
Note: This CL does not enable the thread pool, a separate CL will
enable it.
Bug: 197257926
Test: atest UserLifecycleTests
Change-Id: I76ba673f78b69c7f0caac2d843fa77079e92138a
The new service will intercept all activity starts in communal mode and
enforce that the activity is allowed by ensuring the user has enabled
the package and the activity has showWhenLocked=true.
Test: locally on device
Test: atest FrameworksMockingServicesTests:CommunalManagerServiceTest
Bug: 191994709
Bug: 191996331
Bug: 200324021
Change-Id: I1892881481cf055bd4938d4cf0b624027ec2be3e
Starting the service asynchronously is resulting in a
race condition when accessing a shared data structure.
We could add a lock to guard this data structure but
this is resulting in a slightly worse performance than
starting the service synchronously.
Bug: 194428627
Bug: 179687249
Test: treehugger verification
Change-Id: Ib4d610e8a221f94a3dcc8475371b4a05e5582149
Merged-In: Ib4d610e8a221f94a3dcc8475371b4a05e5582149
(cherry picked from commit 9df4ac6093)
Starting the service asynchronously is resulting in a
race condition when accessing a shared data structure.
We could add a lock to guard this data structure but
this is resulting in a slightly worse performance than
starting the service synchronously.
Bug: 194428627
Bug: 179687249
Test: treehugger verification
Change-Id: Ib4d610e8a221f94a3dcc8475371b4a05e5582149
- Now based on config.enable_sidekick_graphics
Test: build pass, boot test
Bug: 179179780
Bug: 196075234
Change-Id: I032d2cc13f8911c19410f3f3faebef4566825eb9
(cherry picked from commit 511490ab8e7a6b334fab8f613e79f66ba819fc1c)
