Introduces new ApplicationInfo fields to surface zero or more split
APKs for an application. Splice these APKs into both the class
loader and resource system. Cleaner building of these paths.
Run dexopt() on all split APKs found after a parse, and populate
into ApplicationInfo.
Change-Id: I4a376bf4492d84ea95aafa866e106ea43a43e492
The @hide was being ignored because they were being used by the
constructor. Fixed by making the FingerprintManager constructor
hidden.
Change-Id: I3cd409df5055579f5004b08d00d5d951b8e5afd3
This change fixes a bug where native daemons may try to communicate
with the power manager before it was fully initialized due to a race
between publishing the binder service and completing init().
The solution was to simplify the dependencies related to the power
manager. It turns out that most services that were passed in
init are not actually needed until systemReady. What remained
was a dependency on the activity manager to check permissions for
incoming calls. So now we start activity manager first.
However, the activity manager also depends on power manager for
wakelocks. To break the cycle, we now defer initializing the activity
manager's wakelocks until after the power manager has been started.
Cleaned up a bunch of boot-time service dependencies so that we
can have better confidence that they are correctly maintained.
Bug: 13884219
Change-Id: If08e2d7ccd44e7026a72441bb6bd5afd7bb9fffe
We need the transport to tell the system not only what package it's going
to deliver data for next, but also what format that data is in.
Change-Id: I989cf78febf923a4208acb33ed80ccc7869356f5
The existing code for notification manager/listeners uses a oneway
binder api to deliver messages. One problem with this is that
notification objects can sometimes get fairly large, and can bump
into the oneway binder transaction buffer if many happen at once.
To reduce this issue, flip the service into a oneway delivery of
a status bar notification holder, whose wrapped content is then
immediately fetched upon receipt of the one-way message. This moves
the meat of the fetch to be over a two-way interface without changing
the properties of which object is actually sent (a tickle solution
with lookup key would have changed this)
Further research: attempt to chunk notification objects themselves.
They can sometimes transfer hundreds of KB over a binder transaction.
Bug: 15426276
Change-Id: Ib1a1f4ff848c16f80bcf2ae4dfd2b87a9091f0b2
Bug: 15116722
- Select intermediate GL texture size based on available
preview dimensions.
- Fixes for configure deadlock.
- Fixes for jpeg capture.
Change-Id: I3f665230defdad718de40494dd67fda5ea432bfb
Reasons
1) Now that QC is no longer a modal dialog, it doesn't make sense for
to use FLAG_ACTIVITY_CLEAR_WHEN_TASK_RESET. We want QC to stick around
inside the back stack.
2) FLAG_ACTIVITY_CLEAR_WHEN_TASK_RESET is deprecated. It now behaves
completely differently than it used to. It now acts the same as
FLAG_ACTIVITY_NEW_DOCUMENT.
Bug: 15693551
Change-Id: Ia22fe04d7a91876061498bf1f098755b54199704
Everything that used the IdleMaintenance APIs/broadcasts gets to use the
spiffy new JobScheduler instead. Hooray!
On top of that, the now-obsolete "idle maintenance" APIs are now gone
entirely. Double hooray!
Bug 14993295
Change-Id: I5fb67c296ca8cd0ba8a2c8760a0f0d9d962d813b
This adds SurfaceFlinger's app VSYNC offset and buffer deadline
values to DisplayInfo. The values will be available to apps
through queries on a Display object (currently hidden).
Bug 14612039
Change-Id: I48760f58a9d74d99651b02a9d595f420410f2bb5
This is being done in support of preview-less Face Unlock (b/14433919). Nothing
is calling this function yet, but it will be called from a trustlet to tell Face
Unlock to authenticate in the background.
If this is committed before the corresponding Face Unlock change, Face Unlock
will not build because it would not be implementing this function, and it must
implement all functions in the interface in order to build.
Change-Id: I4aaea78d58cc5f1f7e13cb981fb9a217cd901496
Bug 15470128
Bug 15470558
Wait for shared element destinations to be complete
before sending it to the calling activity.
Don't allow layout between setting final destination
and the transition values capture.
Use snapshots to hold the final position while waiting
for the called Activity to take the shared element.
Fixed problem with exiting views sometimes disappearing
when exiting.
Change-Id: Ibc655f7bb9e8dd6e8a15778c96931e3d845cc15c
Bug: 15683945
invokeFunctor() does not require isEnabled() to be true
to execute. Specifically it does not care if HardwareRenderer
has a Surface or not, as it will fall back to a pbuffer surface
if available. If there is no context at all, it will invoke
with kModeProcessNoContext.
Change-Id: Ie6abe566b92c8fa33bb7a673fc3b9fa9ce913446
Without this change, passing a EXTRA_SHOW_FRAGMENT value
for a two panel preferences activity will cause the correct
fragment to be shown. However, it will not cause the
correct header to be highlighted.
Bug: 15675746
Bug: 5045558
Change-Id: I18d8e15dd104e8f39ae1ccbb11ab17fd1bf7462e
