Peter-Easton · November 27, 2020 20:13
diff --git a/Pixel 4 Captive Portal Detection Test b/Pixel 4 Captive Portal Detection Test
 # Pixel 4 Captive Portal Detection Test

 ## Equipment
 Pixel 4 (Flame), running GrapheneOS Build number RP1A.201105.002.2020.11.25.22 Beta Release. The phone is in near-mint condition and has seen little to no use outside being used as a testing device. 

 ### Prior to running the test
 * The phone was factory reset, then connected via private Wi-Fi and allowed to update when the release was pushed to the update server. No third party apps were installed or other software settings were changed.
 * To simulate a daily use device, a pin code of 12345 was set.
 * No SIM card or eSIM was installed, in order to force the phone to connect only via Wi-Fi.
 * Prior to the test being run, the Pixel 4 was paired and verified locally with Auditor using a Pixel 3. The Pixel 3 is currently paired with Attestation Server and is submitting attestation data regularly. The test did not go forward until the Green Screen indicating successful verification with strong pairing was displayed on the Auditing device.

 ## Method
 ### Preparation
 Three separate public locations that had functioning WiFi with captive web portals were travelled to within the same local region. The Wi-Fi was switched on throughout the entire test. Notifications were switched on and the notification volume turned to maximum for ease of testing.

 Any terms and conditions that would be asked by the captive portal were to be accepted. Upon connection, Vanadium was opened in Incognito mode, and then made to connect to https://google.com. Successful connection to https://google.com via Wi-Fi concluded the test.

 ### Expected outcome
 Upon entering Wi-Fi reception range, a notification would be displayed in the notification bar. Connecting to the Wi-Fi network was expected to bring up a captive "Terms and Conditions" web portal in the Webview, during which terms and conditions would be displayed with a prompt to accept them or provide a customer login, prior to being allowed to access the Internet.

 ### Observations
 Anticipated outcome was observed in all tests. Since all three locations were independently tested and working, Captive Portal Detection may be safely assumed to be working in the Pixel 4 Beta channel. 

 ## Notes and warnings
 * A quarter way through the update, while the phone was indicating that it was "Downloading" the update, the Pixel 4 was changed from the Stable channel to the Beta. No other anomalous behaviour was observed.
 * Due to issues related to the SARS-2 COVID19 global pandemic, additional locations were not tested to limit potential exposure.
	# Pixel 4 Captive Portal Detection Test

	## Equipment
	Pixel 4 (Flame), running GrapheneOS Build number RP1A.201105.002.2020.11.25.22 Beta Release. The phone is in near-mint condition and has seen little to no use outside being used as a testing device.

	### Prior to running the test
	* The phone was factory reset, then connected via private Wi-Fi and allowed to update when the release was pushed to the update server. No third party apps were installed or other software settings were changed.
	* To simulate a daily use device, a pin code of 12345 was set.
	* No SIM card or eSIM was installed, in order to force the phone to connect only via Wi-Fi.
	* Prior to the test being run, the Pixel 4 was paired and verified locally with Auditor using a Pixel 3. The Pixel 3 is currently paired with Attestation Server and is submitting attestation data regularly. The test did not go forward until the Green Screen indicating successful verification with strong pairing was displayed on the Auditing device.

	## Method
	### Preparation
	Three separate public locations that had functioning WiFi with captive web portals were travelled to within the same local region. The Wi-Fi was switched on throughout the entire test. Notifications were switched on and the notification volume turned to maximum for ease of testing.

	Any terms and conditions that would be asked by the captive portal were to be accepted. Upon connection, Vanadium was opened in Incognito mode, and then made to connect to https://google.com. Successful connection to https://google.com via Wi-Fi concluded the test.

	### Expected outcome
	Upon entering Wi-Fi reception range, a notification would be displayed in the notification bar. Connecting to the Wi-Fi network was expected to bring up a captive "Terms and Conditions" web portal in the Webview, during which terms and conditions would be displayed with a prompt to accept them or provide a customer login, prior to being allowed to access the Internet.

	### Observations
	Anticipated outcome was observed in all tests. Since all three locations were independently tested and working, Captive Portal Detection may be safely assumed to be working in the Pixel 4 Beta channel.

	## Notes and warnings
	* A quarter way through the update, while the phone was indicating that it was "Downloading" the update, the Pixel 4 was changed from the Stable channel to the Beta. No other anomalous behaviour was observed.
	* Due to issues related to the SARS-2 COVID19 global pandemic, additional locations were not tested to limit potential exposure.