drop bramble alpha/beta workaround instructions
This information is available elsewhere and nearly everyone doing alpha and beta testing on the Pixel 4a (5G) has already dealt with it. Few people are going to see it here especially since it won't be the latest release anymore.
This commit is contained in:
parent
267a9d9a06
commit
bb0fe3d0c7
@ -686,22 +686,6 @@
|
||||
<li><a href="https://github.com/GrapheneOS/platform_manifest/releases/tag/TQ1A.230105.002.2023012500">TQ1A.230105.002.2023012500</a> (Pixel 6, Pixel 6 Pro, Pixel 7 Pro, emulator, generic, other targets)</li>
|
||||
</ul>
|
||||
|
||||
<p>Due to a build issue caused by an upstream Android build system bug, the
|
||||
initial build for the Pixel 4a (5G) pushed out to the Alpha and Beta channels
|
||||
had broken Wi-Fi, Bluetooth and cellular connectivity. A new release has been
|
||||
made available resolving the issue. You can either update to the new release
|
||||
via an over-the-air update using USB tethering from another device or you can
|
||||
<a href="https://releases.grapheneos.org/bramble-ota_update-2023012600.zip">download
|
||||
the release</a> on a computer and then
|
||||
<a href="/usage#updates-sideloading">sideload it</a>. This issue was missed in
|
||||
internal testing and not reported while the release was in Alpha so it slipped
|
||||
through to the Beta channel. This is a nice example of why we have our release
|
||||
channel system but normally it would have been reported in Alpha. We need more
|
||||
Alpha testers who join #testing:grapheneos.org on Matrix, update when releases
|
||||
get announced there and report any issues. We received positive testing
|
||||
reports from at least one device from each generation but the issue only
|
||||
impacted the Pixel 4a (5G).</p>
|
||||
|
||||
<p>Changes since the 2023011000 release:</p>
|
||||
|
||||
<ul>
|
||||
|
Loading…
x
Reference in New Issue
Block a user