| b56fe9f1071c1506d996f8c8e1da780b607fea78 |
|
17-Jun-2017 |
Sen Jiang <senj@google.com> |
Use the prefix in product_id for system_id.
If product id is "android-things-test:123", but system id is
"android-things:som-rpi3", we change the system id to
"android-things-test:som-rpi3".
This is needed for devconsole testing to isolate test environment
with production.
Also added unittest for image_properties_android.cc
Bug: 62466250
Test: check system_id in Omaha request
Test: update_engine_unittests
Change-Id: Ib97573e117c0fecf85922260e6e75e63e36c18e3
(cherry picked from commit 98c0751f0dc970cadfc8014883018524dd8899f1)
/system/update_engine/image_properties_android.cc
|
| 1d5d95ffd80c96de1ca488f6c87a6f54301dadf3 |
|
19-May-2017 |
Sen Jiang <senj@google.com> |
Report build_type to Omaha.
Send additional os_build_type <app> attribute to distinguish between
user and userdebug images.
Bug: 36491462
Test: check omaha request xml
Change-Id: I519e85293db9a2194e0cd015a3a944adc723c3dd
(cherry picked from commit eba2297072914582aed5008ad5f99374124ae4d7)
/system/update_engine/image_properties_android.cc
|
| 94a4decc032ce0cbe44514436f99cdadbc807436 |
|
29-Mar-2017 |
Sen Jiang <senj@google.com> |
Send both system id and product id to Omaha.
The request will have two <app> with different app_id and version.
Test: observe request in the log
Change-Id: I51b0dcf3c0affc81fe152ff24ce0ccc9a36e6385
(cherry picked from commit 573919d54a8421f1b2147d801ae4104adebf5cd7)
/system/update_engine/image_properties_android.cc
|
| ebf6e1228e6e42c19334bb8b3da62f4aef105dea |
|
11-Mar-2017 |
Alex Deymo <deymo@google.com> |
Send the system image build fingerprint and bootloader versions.
In Android, we had STUBS for the bootloader (firmware) version, board,
and EC version. This patch populates those versions and strings based on
the system props using Android standard properties and includes the full
build.fingerprint in the request, which could be used to double-check
the request.
Bug: 35364971
Test: `update_engine_client --check_for_update` sends all this
information now.
(cherry picked from commit 094ce0bec1de7952e2ddc6c0f3c94dc3615b99c0)
Change-Id: I8265c5b8f4415f825160ea259c5b84b4b77372d7
/system/update_engine/image_properties_android.cc
|
| 983f5780ca5f5bded3838fc94bf333551cc59538 |
|
22-Feb-2017 |
Sen Jiang <senj@google.com> |
Report combined system version and product version.
The version now consists of system version (3 numbers) and product
version (1 number).
Bug: 35364984
Test: checked the omaha ping in logcat on edison
Change-Id: Id479682f84d66da7eb6d2b8ce92c44f29ac6e3da
/system/update_engine/image_properties_android.cc
|
| 39910dcd1d68987ccee7c3031dc269233a8490bb |
|
10-Nov-2015 |
Alex Deymo <deymo@google.com> |
Split payload application code into a subdirectory.
This patch splits from the main libupdate_engine code the part that
is strictly used to download and apply a payload into a new static
library, moving the code to subdirectories. The new library is divided
in two subdirectories: common/ and payload_consumer/, and should not
depend on other update_engine files outside those two subdirectories.
The main difference between those two is that the common/ tools are more
generic and not tied to the payload consumer process, but otherwise they
are both compiled together.
There are still dependencies from the new libpayload_consumer library
into the main directory files and DBus generated files. Those will be
addressed in follow up CLs.
Bug: 25197634
Test: FEATURES=test emerge-link update_engine; `mm` on Brillo.
Change-Id: Id8d0204ea573627e6e26ca9ea17b9592ca95bc23
/system/update_engine/image_properties_android.cc
|
| 856166594771c61973856f563e622ccb7dd48aa1 |
|
16-Oct-2015 |
Alex Deymo <deymo@google.com> |
Read ProductId, ProductVersion and Channel setting in Brillo.
The ProductId, ProductVersion and current/target channels are specified
in a very different way in Brillo compared to Chrome OS. This patch
moves the logic to read and parse /etc/lsb-release in Chrome OS to a
new image_properties module and implements the equivalent module in
Brillo.
This new module replaces some of the logic previously in the
OmahaRequestParams class, both for parsing the read-only properties
from the rootfs and parsing and storing the target channel in the
stateful partition. The Chrome OS version of the new module keeps the
same behavior, except that it falls back to "stable-channel" if the
the current channel is missing in the rootfs (unlikely in Chrome OS).
On the other hand, the new Brillo implementation reads these settings
from the /etc/osrelease file and /etc/osrelease.d directory and doesn't
allow to override those setting during development. The persisted
target_channel and powerwash_allowed settings are stored in Prefs
as many other settings. Finally, since Brillo images don't contain
a channel name baked in the image, we store the channel name where we
got the image from at the time of the update. The first boot after
provisioning will default to "stable-channel".
Bug: 25013069
Test: unittest in Chrome OS; `mm` and tested on a Brillo device.
Change-Id: Icc114b8098af3edaaba715c9c2e3ebe9f417c876
/system/update_engine/image_properties_android.cc
|