4fe4b2e65d68f09bf14601b0ab3b3ea90cc1ed4c
Role holders can request an update. When that happens, the flow returns back to platform, platform performs the update and checks the update result. If update was successful, it restared the role holder, and if not, it failed provisioning. This CL updates this so that the role holder is _always_ started, regardless of the update result. That way the role holder can make a decision whether to continue provisioning or fail it. Bug: 224993192 Test: none Change-Id: Ia7dd61d02c568e8c8ad17af0a61106d127c4869a
…
Merge "Revert "Disable pointer authentication in app processes."" am:
b9fc2910ca am: a236c37517 am: 95dc32f484
…
…
…
Merge "Curve 25519: Support use via Android Keystore provider (part 1)" am:
bab26cc607 am: 050d61f1b3 am: 8249f4a893
…
…
…
…
Merge "Remove broken code for mounting encrypted OBB files" am:
a4f24f08b0 am: 56c37e5778 am: 089a351d31
…
…
…
…
…
…
Merge "Add tool for injecting tracing code into a method." am:
a7006818d3 am: 3e53e056ee am: 152a78bd50
…
…
…
…
Description
No description provided
Languages
Java
73.7%
Kotlin
14%
PowerBuilder
5.8%
C++
5.2%
AIDL
1%