From 90f4c364f3afa5bf5f4db873d522b0cbecd89c29 Mon Sep 17 00:00:00 2001 From: Daniel Micay Date: Fri, 5 Jun 2020 22:12:02 -0400 Subject: [PATCH] explain update server metadata --- static/build.html | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/static/build.html b/static/build.html index 86db00d6..42c3edb9 100644 --- a/static/build.html +++ b/static/build.html @@ -644,6 +644,24 @@ cd ../.. factory images. See the usage guide section on sideloading updates for information on how to use the update packages.

+

Running script/release.sh also generates channel metadata for the + update server. If you configured the Updater client URL and set the build to include + it (see the information on OFFICIAL_BUILD above), you can push signed + over-the-air updates via the update system. Simply upload the update package to the + update server along with the channel metadata for the release channel, and it will be + pushed out to the update client. The $DEVICE-beta and + $DEVICE-stable metadata provide the Beta and Stable release channels used + by the update client. The $DEVICE-testing metadata provides + provides an internal testing channel for the OS developers, which can be temporarily + enabled using adb shell setprop sys.update.channel testing. The name is + arbitrary and you can also use any other name for internal testing channels. For + GrapheneOS itself, the testing channel is used to push out updates to developer + devices, followed by a sample future release to test that the release which is about + to be pushed out to the Beta channel is able to update to a future release. Once it's + tested internally, the release is pushed out to the Beta channel, and finally to the + Stable channel after public testing. A similar approach is recommended for derivatives + of GrapheneOS.

+

Generating delta updates