use Pixel 5 for examples in build documentation

This commit is contained in:
Daniel Micay 2021-08-11 05:37:09 -04:00
parent a8293b0269
commit 94b58830b3

View File

@ -410,12 +410,12 @@ cd ../..</pre>
running the submodule commands for other devices as they will simply not do
anything.</p>
<p>For example, to build the kernel for blueline:</p>
<p>For example, to build the kernel for redfin:</p>
<pre>cd kernel/google/crosshatch
<pre>cd kernel/google/redbull
git submodule sync
git submodule update --init --recursive
./build.sh blueline</pre>
./build.sh redfin</pre>
</section>
<section id="setting-up-the-os-build-environment">
@ -428,9 +428,9 @@ git submodule update --init --recursive
<pre>source script/envsetup.sh</pre>
<p>Select the desired build target (<code>sunfish</code> is the Pixel 4a):</p>
<p>Select the desired build target (<code>redfin</code> is the Pixel 5):</p>
<pre>choosecombo release sunfish user</pre>
<pre>choosecombo release redfin user</pre>
<p>For a development build, you may want to replace <code>user</code> with
<code>userdebug</code> in order to have better debugging support. Production builds
@ -570,11 +570,11 @@ mv vendor/android-prepare-vendor/DEVICE/BUILD_ID/vendor/google_devices/* vendor/
<p>The encryption passphrase for all the keys generated for a device needs to
match for compatibility with the GrapheneOS scripts.</p>
<p>To generate keys for sunfish (you should use unique keys per device
<p>To generate keys for redfin (you should use unique keys per device
variant):</p>
<pre>mkdir -p keys/sunfish
cd keys/sunfish
<pre>mkdir -p keys/redfin
cd keys/redfin
../../development/tools/make_key releasekey '/CN=GrapheneOS/'
../../development/tools/make_key platform '/CN=GrapheneOS/'
../../development/tools/make_key shared '/CN=GrapheneOS/'
@ -589,7 +589,7 @@ cd ../..</pre>
<p>Generate a signify key for signing factory images:</p>
<pre>signify -G -n -p keys/sunfish/factory.pub -s keys/sunfish/factory.sec</pre>
<pre>signify -G -n -p keys/redfin/factory.pub -s keys/redfin/factory.sec</pre>
<p>Remove the <code>-n</code> switch to set a passphrase. The <code>signify</code>
tool doesn't provide a way to change the passphrase without generating a new key, so
@ -604,7 +604,7 @@ cd ../..</pre>
<p>You can (re-)encrypt your signing keys using the <code>encrypt_keys</code> script,
which will prompt for the old passphrase (if any) and new passphrase:</p>
<pre>script/encrypt_keys.sh keys/sunfish</pre>
<pre>script/encrypt_keys.sh keys/redfin</pre>
<p>The <code>script/decrypt_keys.sh</code> script can be used to remove encryption,
which is not recommended. The script exists primarily for internal usage to decrypt
@ -646,10 +646,10 @@ cd ../..</pre>
<p>Generate a signed release build with the release.sh script:</p>
<pre>script/release.sh sunfish</pre>
<pre>script/release.sh redfin</pre>
<p>The factory images and update package will be in
<code>out/release-sunfish-$BUILD_NUMBER</code>. The update zip performs a full OS
<code>out/release-redfin-$BUILD_NUMBER</code>. 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 <code>target_files</code> zips and generating
@ -692,34 +692,34 @@ cd ../..</pre>
delta updates by passing the device, source version build number and target version
build number. For example:</p>
<pre>script/generate_delta.sh sunfish 2020.12.12.03 2021.01.05.03</pre>
<pre>script/generate_delta.sh redfin 2021.08.03.03 2021.08.09.02</pre>
<p>The script assumes that the releases are organized in the following directory
structure:</p>
<pre>releases
├── 2020.12.12.03
│   └── release-sunfish-2020.12.12.03
├── 2021.08.03.03
│   └── release-redfin-2021.08.03.03
│   ├── otatools
│   ├── sunfish-beta
│   ├── sunfish-factory-2020.12.12.03.zip
│   ├── sunfish-factory-2020.12.12.03.zip.sig
│   ├── sunfish-img-2020.12.12.03.zip
│   ├── sunfish-ota_update-2020.12.12.03.zip
│   ├── sunfish-stable
│   ├── sunfish-target_files-2020.12.12.03.zip
│   └── sunfish-testing
└── 2021.01.05.03
└── release-sunfish-2021.01.05.03
│   ├── redfin-beta
│   ├── redfin-factory-2021.08.03.03.zip
│   ├── redfin-factory-2021.08.03.03.zip.sig
│   ├── redfin-img-2021.08.03.03.zip
│   ├── redfin-ota_update-2021.08.03.03.zip
│   ├── redfin-stable
│   ├── redfin-target_files-2021.08.03.03.zip
│   └── redfin-testing
└── 2021.08.09.02
└── release-redfin-2021.08.09.02
├── otatools
├── sunfish-beta
├── sunfish-factory-2021.01.05.03.zip
├── sunfish-factory-2021.01.05.03.zip.sig
├── sunfish-img-2021.01.05.03.zip
├── sunfish-ota_update-2021.01.05.03.zip
├── sunfish-stable
├── sunfish-target_files-2021.01.05.03.zip
└── sunfish-testing</pre>
├── redfin-beta
├── redfin-factory-2021.08.09.02.zip
├── redfin-factory-2021.08.09.02.zip.sig
├── redfin-img-2021.08.09.02.zip
├── redfin-ota_update-2021.08.09.02.zip
├── redfin-stable
├── redfin-target_files-2021.08.09.02.zip
└── redfin-testing</pre>
<p>Incremental updates are uploaded alongside the update packages and update metadata
on the static web server used as an update server. The update client will