Skip to content

Instantly share code, notes, and snippets.

View Peter-Easton's full-sized avatar
🏴‍☠️
Arr!

JollyRoger Peter-Easton

🏴‍☠️
Arr!
  • Treasure Island, The High Seas
View GitHub Profile
@Peter-Easton
Peter-Easton / grapheneos-shopping-list.md
Last active November 6, 2024 21:57
Your GrapheneOS Shopping List

Your GrapheneOS Shopping List

Software

Operating System

Building has been done successfully on the following operating systems:

  • Debian Buster 10
  • Ubuntu LTS 18.04
  • Arch Linux
  • Fedora 30
CTS results on Pixel3 (Blueline) running GrapheneOS QQ2A.200501.001.B2 BETA Android 10 with 81.0.4044.117 monochrome_public_apk as the Webview and browser
* CtsAbiOverrideHostTestCases - pass
* CtsAccelerationTestCases - pass
* CtsAccessibilityServiceTestCases - pass
* CtsAccessibilityTestCases - pass
* CtsAccountManagerTestCases - pass
* CtsActivityManagerBackgroundActivityTestCases - fail
org.junit.runners.model.TestTimedOutException: test timed out after 300000 milliseconds
at libcore.io.Linux.readBytes(Native Method)
CTS results on Pixel3 (Blueline) running GrapheneOS QQ2A.200501.001.B2 BETA Android 10 with 83.0.4103.60 monochrome_public_apk as the Webview and browser
* CtsAbiOverrideHostTestCases - pass
* CtsAccelerationTestCases - pass
* CtsAccessibilityServiceTestCases - pass
* CtsAccessibilityTestCases - pass
* CtsAccountManagerTestCases - pass
* CtsActivityManagerBackgroundActivityTestCases - fail - may be due to the CTS not installing/uninstalling its testing apps correctly.
org.junit.runners.model.TestTimedOutException: test timed out after 300000 milliseconds
at libcore.io.Linux.readBytes(Native Method)
@Peter-Easton
Peter-Easton / QQ3A.200605.001.2020.06.02.02.txt
Created June 5, 2020 23:39
QQ3A.200605.001.2020.06.02.02 CTS Test
CTS results on Pixel 3 (Blueline) running GrapheneOS QQ3A.200605.001.2020.06.02.02 BETA (Android 10 with Vanadium 83.0.4103.83 as the Webview and browser
* CtsAbiOverrideHostTestCases - pass
* CtsAccelerationTestCases - pass
* CtsAccessibilityServiceTestCases - pass
* CtsAccessibilityTestCases - pass
* CtsAccountManagerTestCases - pass
* CtsActivityManagerBackgroundActivityTestCases - fail - this may be being caused by the cts tripping over itself.
org.junit.runners.model.TestTimedOutException: test timed out after 300000 milliseconds
at libcore.io.Linux.readBytes(Native Method)
CTS results on PIXEL 4 (FLAME) running GrapheneOS QQ3A.200605.001.2020.06.22.21 BETA (10 with Vanadium 83.0.4103.106 as the Webview and browser
* CtsAbiOverrideHostTestCases - pass
* CtsAccelerationTestCases - pass
* CtsAccessibilityServiceTestCases - pass
* CtsAccessibilityTestCases - pass
* CtsAccountManagerTestCases - pass
* CtsActivityManagerBackgroundActivityTestCases - pass
* CtsAdminPackageInstallerTestCases - pass
* CtsAdminTestCases - pass
@Peter-Easton
Peter-Easton / flame-QQ3A.200705.002.2020.07.06.20.txt
Created July 19, 2020 07:49
CTS results on Pixel 4 (flame) running GrapheneOS QQ3A.200705.002.2020.07.06.20 EXPERIMENTAL (10 with Vanadium 83.0.4103.106 apk_release as the Webview and browser
CTS results on Pixel 4 (flame) running GrapheneOS QQ3A.200705.002.2020.07.06.20 EXPERIMENTAL (10 with Vanadium 83.0.4103.106 apk_release as the Webview and browser
* CtsAbiOverrideHostTestCases - pass
android.accessibilityservice.cts.AccessibilityWindowQueryTest#testFindPictureInPictureWindow
* CtsAccelerationTestCases - pass
* CtsAccessibilityServiceTestCases - pass
* CtsAccessibilityTestCases - pass
* CtsAccountManagerTestCases - pass
* CtsActivityManagerBackgroundActivityTestCases - pass
* CtsAdminPackageInstallerTestCases - pass
# Pixel 3 Phone Clock App Test, Part 1
## Equipment
Pixel 3, running GrapheneOS Build number RP1A.201105.002.2020.11.03.03 Stable Release. The phone has seen extensive use but is in good cosmetic condition. Vibration, sound, speakers, microphones, and cameras have been verified to be in good operational condition as of yesterday.
## Method
### Preparation
The phone's battery was discharged to nearly 50% prior to the test. Call Volume, Ring and Notification Volume, and Alarm Volumes were set to 100%, while Media Volume was left near 25%. Bluetooth was switched off. The Phone was connected to a WiFi network and has a valid SIM card with cellular data access.
### Process
# Pixel 3 Phone Clock App Test, Part 2
## Equipment
Pixel 3, running GrapheneOS Build number RP1A.201105.002.2020.11.03.03 Stable Release. The phone has seen extensive use but is in good cosmetic condition. Vibration, sound, speakers, microphones, and cameras have been verified to be in good operational condition as of yesterday.
## Method
### Preparation
The phone's battery was charged to nearly 90% prior to the test. Call Volume, Ring and Notification Volume, and Alarm Volumes were set to 100%, while Media Volume was left near 25%. Bluetooth was switched off. The Phone was connected to a WiFi network and has a valid SIM card with cellular data access.
Part 1 of the clock app test was run prior to this test. The phone was not shut down between tests.
# Pixel 3 Phone Clock App Test, Part 2
## Equipment
Pixel 3, running GrapheneOS Build number RP1A.201105.002.2020.11.03.03 Stable Release. The phone has seen extensive use but is in good cosmetic condition. Vibration, sound, speakers, microphones, and cameras have been verified to be in good operational condition as of yesterday.
## Method
### Preparation
The phone's battery was charged to nearly 90% prior to the test. Call Volume, Ring and Notification Volume, and Alarm Volumes were set to 100%, while Media Volume was left near 25%. Bluetooth was switched off. The Phone was connected to a WiFi network and has a valid SIM card with cellular data access.
Part 2 of the clock app test was run prior to this test. The phone was not shut down between tests.
# Pixel 3 Phone Clock App Test, Part 4
## Equipment
Pixel 3, running GrapheneOS Build number RP1A.201105.002.2020.11.05.18 Stable Release. The phone has seen extensive use but is in good cosmetic condition. Vibration, sound, speakers, microphones, and cameras have been verified to be in good operational condition as of yesterday.
## Method
### Preparation
The phone's battery was discharged to nearly 80% prior to the test. Call Volume, Ring and Notification Volume, and Alarm Volumes were set to 100%, while Media Volume was left near 25%. Bluetooth was switched off. The Phone was connected to a WiFi network and has a valid SIM card with cellular data access.
After being prompted for the update, the phone was restarted via the "restart" option in the power menu.