From 37253ffa17c63ea3fd0c201fa4e62ee36e5ce2ff Mon Sep 17 00:00:00 2001 From: smdyv <88971341+smdyv@users.noreply.github.com> Date: Thu, 25 Aug 2022 15:05:41 +0200 Subject: Add highlighting style for placeholders This is in accordance with Google's developer documentation style guide. --- static/build.html | 50 +++++++++++++++++++++++++------------------------- 1 file changed, 25 insertions(+), 25 deletions(-) (limited to 'static/build.html') diff --git a/static/build.html b/static/build.html index 44942767..3fbe60c6 100644 --- a/static/build.html +++ b/static/build.html @@ -354,9 +354,9 @@ repo sync -j16 tag for a device. For devices without official support, use the latest tag marked as being appropriate for generic / other devices in the release notes.

- 
mkdir grapheneos-TAG_NAME
-cd grapheneos-TAG_NAME
-repo init -u https://github.com/GrapheneOS/platform_manifest.git -b refs/tags/TAG_NAME
+ 
mkdir grapheneos-TAG_NAME
+cd grapheneos-TAG_NAME
+repo init -u https://github.com/GrapheneOS/platform_manifest.git -b refs/tags/TAG_NAME

Verify the manifest:

@@ -489,13 +489,13 @@ source script/envsetup.sh m aapt2

Extract the vendor files corresponding to the matching release with - DEVICE and BUILD_ID replaced with the + DEVICE and BUILD_ID replaced with the appropriate values:

-
vendor/adevtool/bin/run download vendor/adevtool/dl/ -d DEVICE -b BUILD_ID -t factory ota
-sudo vendor/adevtool/bin/run generate-all vendor/adevtool/config/DEVICE.yml -c vendor/state/DEVICE.json -s vendor/adevtool/dl/DEVICE-BUILD_ID-*.zip
+
vendor/adevtool/bin/run download vendor/adevtool/dl/ -d DEVICE -b BUILD_ID -t factory ota
+sudo vendor/adevtool/bin/run generate-all vendor/adevtool/config/DEVICE.yml -c vendor/state/DEVICE.json -s vendor/adevtool/dl/DEVICE-BUILD_ID-*.zip
 sudo chown -R $(logname):$(logname) vendor/google_devices
-vendor/adevtool/bin/run ota-firmware vendor/adevtool/config/DEVICE.yml -f vendor/adevtool/dl/DEVICE-ota-BUILD_ID-*.zip

+vendor/adevtool/bin/run ota-firmware vendor/adevtool/config/DEVICE.yml -f vendor/adevtool/dl/DEVICE-ota-BUILD_ID-*.zip
@@ -716,7 +716,7 @@ cd ../.. 
script/release.sh raven

The factory images and update package will be in - out/release-raven-$BUILD_NUMBER. The update zip performs a full OS + out/release-raven-BUILD_NUMBER. The update zip performs a full OS installation so it can be used to update from any previous version. More efficient incremental updates are used for official over-the-air GrapheneOS updates and can be generated by keeping around past signed target_files zips and generating @@ -732,9 +732,9 @@ cd ../.. 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 + 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 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.

@@ -804,7 +804,7 @@ cd ../.. 
git clone https://github.com/GrapheneOS/Vanadium.git
 cd Vanadium
-git checkout $CORRECT_BRANCH_OR_TAG
+git checkout CORRECT_BRANCH_OR_TAG

Generate a signing key for Vanadium if this is the initial build:

@@ -818,12 +818,12 @@ git checkout $CORRECT_BRANCH_OR_TAG 
fetch --nohooks android
-

Sync to the latest stable release for Android (replace $VERSION with +

Sync to the latest stable release for Android (replace VERSION with the correct value):

cd src
 git fetch --tags
-git checkout $VERSION
+git checkout VERSION

Apply the GrapheneOS patches on top of the tagged release:

@@ -889,12 +889,12 @@ git checkout $VERSION packages/apps/Updater/res/values/config.xml. See above for details on including the Updater app in a release. These are the relevant files:

- 
$DEVICE-ota_update-$BUILD_NUMBER.zip
-$DEVICE-factory-BUILD_NUMBER.zip
-$DEVICE-factory-BUILD_NUMBER.zip.sig
-$DEVICE-testing
-$DEVICE-beta
-$DEVICE-stable
+ 
DEVICE-ota_update-BUILD_NUMBER.zip
+DEVICE-factory-BUILD_NUMBER.zip
+DEVICE-factory-BUILD_NUMBER.zip.sig
+DEVICE-testing
+DEVICE-beta
+DEVICE-stable

Generally, you should start by uploading the ota_update, factory images and testing channel metadata.

@@ -904,9 +904,9 @@ $DEVICE-stable arbitrary names. You can override the release channel configured in the update client via ADB with the following command:

- 
adb shell setprop sys.update.channel channel_name
+ 
adb shell setprop sys.update.channel CHANNEL_NAME
-

Replace channel_name with the name of the release channel, such as +

Replace CHANNEL_NAME with the name of the release channel, such as testing.

After pushing out and testing the new release via the internal release channel, @@ -1136,9 +1136,9 @@ rm android-cts-media-1.5.zip

To obtain a list of CTS modules:

list modules

To run a specific module and avoid wasting time capturing device information:

- 
run cts --skip-device-info --module CtsModuleName
+ 
run cts --skip-device-info --module CTS_MODULE_NAME

To speed up initialization after running some initial tests:

- 
run cts --skip-device-info --skip-preconditions --module CtsModuleName
+ 
run cts --skip-device-info --skip-preconditions --module CTS_MODULE_NAME

It's possible to run the whole standard CTS plan with a single command, but running specific modules is recommended, especially if you don't have everything set up for the entire test suite.

@@ -1165,7 +1165,7 @@ rm android-cts-media-1.5.zip the build number, which is generally incorporated into the build. For example, even without a platform-tools tag, you can obtain the build number from adb version or fastboot version. Their version output uses the format - $VERSION-$BUILD_NUMBER such as 30.0.3-6597393 for the + VERSION-BUILD_NUMBER such as 30.0.3-6597393 for the version 30.0.3 where the official release had the build number 6597393. You can obtain the manifest properties with the appropriate repository revisions from ci.android.com with a URL like this: -- cgit v1.3.1