The snapshots are no longer needed after restore is done.
We do this in keeping with the fact that apk/apex code data is
deleted immediately after the rollback is committed.
See go/rollbackmanager-snapshot-deletion for more details.
Bug: 151805360
Test: N/A. Will be added in the next CL.
Change-Id: I5a7540aa08922c4b0c617c9cb37e1bec2ff23fc1
Modules contributing mainline modules (APK/APEX) should set
min_sdk_version as well as apex_available.
For now setting min_sdk_version doesn't change build outputs.
But build-time checks will be added soon.
Exempt-From-Owner-Approval: cherry-pick from internal
Bug: 152655956
Test: m
Merged-In: Ib7685f5f4f924ac145eb4f10ad83a6c0548b2206
Change-Id: Ib7685f5f4f924ac145eb4f10ad83a6c0548b2206
(cherry picked from commit 54042e0ae4)
When cmd is called with the -w flag, it will call ServiceManager::waitForService instead of checkService. This will make dynamic services start and block until they are ready for use.
Bug: 149526916
Test: atest ApexRollbackTests (with and without this flag applied within for dynamic apexd)
Change-Id: Iad0c3d7aa75e5830da10a84bd753d3011438259f
Merged-In: Iad0c3d7aa75e5830da10a84bd753d3011438259f
(cherry picked from commit 77f83368b1)
Let linux clean it up, since this may be accessed by some threads after
the main thread is destructed.
Bug: 154507808 # longterm
Bug: 156785633
Test: w/ repro which calls defaultServiceManager off main thread
Change-Id: Ic109f4bdca3893e6b0b192ac27f3ff03ada6f9e2
The actual problem is that default implementation is set globally.
setDefaultImpl might not work as expected when it is called twice with
different instances.
Because we don't have a proper solution for the problem, we prevent
calling setDefaultImpl() twice by aborting.
Bug: 140139809
Test: ./runtests.sh (in /system/tools/aidl)
Change-Id: I659d3eaad3a45dcba608fa79a08f083f84bc4d58
Previously the background thread for managing EglImages was intialized
as a member variable before the constructor completed running. In very
rare circumstances this can potentially stop the running thread if the
thread ran before mRunning was initialized. To be less error-prone,
require that ImageManger::initThread be explicitly called to guarantee
that class member variables are well-defined when the thread begins
executing.
In case the issue resurfaces after this change, added a debug log to add
context.
Bug: 146416748
Bug: 155852355
Test: builds. There is no reliable repro, so this fix is speculative
Test: systrace to verify thread is running and configured correctly.
Change-Id: I141c86240b90c7f87c22b3768c2e188293987b76
Merged-In: I141c86240b90c7f87c22b3768c2e188293987b76
swapBuffers is called even for device composition when a flip client
target request is present. dequeueBuffer call is skipped
as there is no client composition. This is fine for single display
but if multiple display i.e. vds is present, this will be an issue
as current surface will not be switched and swapBuffers will fail
When flip client target request is present, make sure buffer is
dequeued before swapBuffers.
Bug: 151698217
Test: atest libsurfaceflinger_unittest
Change-Id: I933cbae2f09f81eef6555b1bb1e5991d2c450930
Merged-In: Ia8a1470affb2596b27986cc4153417f48cf4ed1c
When analyzing profiles for dexopt, use the boot image profile format
if the system is configured to profile the boot image.
Test: atest installd_dexopt_test
Bug: 155423653
(cherry-picked from commit: c8a0442cad)
Merged-In: I83ff959389bafcfce291485f78e1b05d6ca42625
Change-Id: I83ff959389bafcfce291485f78e1b05d6ca42625
For easy transition from SchedTune to UtilClamp, direct access to these
cgroups should be abstracted by using task profiles. Replace writepid
commands with new task_profiles command.
Bug: 155419956
Test: change .rc file and confirm task profile is applied
Signed-off-by: Suren Baghdasaryan <surenb@google.com>
Change-Id: I3e06e25a75cf79674d8381b3356c64790fd5a597
These logs are critical to understand the operation of the system, and
do not spam (1/hal start or 1/hal request). Most importantly, if a
manifest fails to be read for whatever reason, this is logged (null
manifest case).
Bug: 151696835
Test: boot, and verify logs of successful hal retrivals
Test: boot, and verify logs w/ patch which causes VINTF to fail the
first time, and verify that this causes a single crash which gives us
the ability to still find and detect a critical error, but allows the
system functionality to continue to work.
Change-Id: I0a26b875947878656d6eda03ffebce97ebb6139e
See details in TODO.
This hack is either causing a bug or may be preventing us from solving
another bug. Until the more critical bug can be fixed, avoiding
early-boot reads of VINTF manifest files.
Bug: 151696835
Test: run, boot, check manifest logs that HAL services register
Change-Id: Iba34afe451026a30e695d6728b4172007aaf7fbd
I've had a CL a long time which did this here:
https://android-review.googlesource.com/c/platform/frameworks/native/+/1225405/
However, I am not sure how to get confidence in it, and it changes
threading structure, scheduling structure, etc... So I don't think it's
quite the right time to merge it yet.
Bug: n/a
Test: n/a
Change-Id: I83549b920a470387484245587a4714b69765f03f
Remove unnecessary semicolon to avoid a warning about C++98
incompatibility:
error: extra ';' outside of a function is incompatible with
C++98 [-Werror,-Wc++98-compat-extra-semi]
Test: Built an AIDL interface with trace.h methods, ran on device, collected traces.
Change-Id: I307a36eeef861d4c28aa85dc3e0b15500bfac7c8
