5b5fa8b412312a41cfd4d7ab475b54d4f730ed2a |
|
07-Oct-2016 |
Alex Deymo <deymo@google.com> |
Add {Get,Set}CohortHint interface. Export the "cohort hint" getter and setter in the client interfaces (D-Bus and Binder). The cohort hint is sent to Omaha on every update check request but can be ignored and/or reset by Omaha on every response. Other minor linter fixes to the affected files. Bug: 31740109 Test: Build with D-Bus and with Binder. Change-Id: I93214f6ffb8662c238b3351e52bf2bdf23e46a9c
/system/update_engine/client_library/client_dbus.h
|
b3fa53bf760bd0a6fd1ef9df28cb425586d733f6 |
|
19-Apr-2016 |
Alex Deymo <deymo@google.com> |
Parse and expose end-of-life flag. Omaha update or noupdate response can include _key=value pairs with arbitrary data. One of those key can be "_eol" with the one of the values "supported", "security-only" or "eol" which notifies the device the end-of-life status of the device with respect to updates. This information is now exposed via GetEolStatus() to the client so it can be properly displayed in the UI. Bug: 27924505 TEST=Added unittest. Run `update_engine_client --eol_status` on link. Change-Id: Icc15f25b4d0b19cc894f5afc52ac7c43c7818982
/system/update_engine/client_library/client_dbus.h
|
2997173235e88c5e4cb13d2844f74afc7b25d6e2 |
|
05-Feb-2016 |
Shuqian Zhao <shuqianz@google.com> |
Add a feature to get the last UpdateAttempt ErrorCode from update_engine For autotest, update_engine test failures are always hard to debug, since the error message is not clear. Add a new flag 'last_attempt_error' to get the last UpdateAttempt ErrorCode from update_engine. Bug:25598547 Test:emerge-peppy update_engine emerge-peppy update_engine_client cros flash a test image to DUT. (on the DUT):update_engine_client --last_attempt_error Compare the results with the update_engine logs, matched. Change-Id: Id12681097ed30b0826cad68809f17f934a07e5b2
/system/update_engine/client_library/client_dbus.h
|
492eaf5067c88db3477538d935ffb0a0ec0c1936 |
|
02-Feb-2016 |
Alex Deymo <deymo@google.com> |
client: Fix the build when using the client dbus interface. Bug: None TEST=`mmma system/update_engine` on edison-eng with dbus disabled Change-Id: I8ca9318cd1626f2bb17db15cb4d6c92511e9d970
/system/update_engine/client_library/client_dbus.h
|
a715f7b8a211b5c4b74206539e9aa7ddacf4b243 |
|
30-Jan-2016 |
Casey Dahlin <sadmac@google.com> |
Properly handle handler registering and unregistering In addition to now supporting unregistering, we now correctly support multiple handlers under DBus, and correctly send initial events under binder. TEST=Verified update_engine_client still works as expected Bug: None Change-Id: I60955d4d9ca61dfe7857b9fc78f77fa4292ed218
/system/update_engine/client_library/client_dbus.h
|
40892497a9b1ea124058baf09f5f2873a15cb696 |
|
26-Jan-2016 |
Casey Dahlin <sadmac@google.com> |
Make client use binder interface on brillo TEST=Verified status and update commands Bug: 25908638 Change-Id: I7994de41001b4e116bffa539f23f1344ab1deae9
/system/update_engine/client_library/client_dbus.h
|
a93cd53c4f8ab8cb926ed9223373567ebbf45cb6 |
|
15-Jan-2016 |
Casey Dahlin <sadmac@google.com> |
Introduce brillo binder interface This is more or less an exact analogue of the DBus interface, but available over binder. We also add support to the client library and let update_engine_client build with binder. We don't yet support an equivalent of the status signal/the HandleStatusUpdate method. That will come in a future CL. Bug: 25908638 TEST=Verified update_engine_client functionality Change-Id: Ic793619c8019b0d50aa184e0f592b6a9ab71e0b0
/system/update_engine/client_library/client_dbus.h
|