update testing docs

_src/android/android-enterprise-device-support.md

@@ -14,43 +14,31 @@ eleventyNavigation:
 discourse_permalink:
     - 'https://discuss.bayton.org/t/android-enterprise-device-testing/28'
 ---
-<div class="callout callout-warning">
 
-### No longer maintained
-
-While I am still actively testing devices, I no longer publish them here. Consider the below to be historical, including the advanced testing, and not to be taken as current status of a device. If you’d like your devices tested against Android Enterprise functionality, feel free to get in touch. 
-
-</div>
-
-The devices listed below have been tested against a current, Android Enterprise-compatible Enterprise Mobility Management (EMM) platform for one or more of the following:
+The devices listed below have been tested against a current (at the time of publishing), Android Enterprise-compatible Enterprise Mobility Management (EMM) platform for one or more of the following:
 
 - Android Enterprise work profile
 - Android Enterprise fully managed (work-managed)
-- Android Enterprise work profile on a fully managed device (COPE/COMP)
+- Android Enterprise work profile on a company owned device (COPE/COMP)
 - Android Enterprise dedicated (COSU or kiosk)
 - Multiple provisioning methods, including [zero-touch enrolment](/android/what-is-android-zero-touch-enrolment/)
 
 <div class="callout callout-info">
 
 ### OEM or reseller?
 
-I welcome additional devices for testing! If you’re an **OEM** or **reseller** of Android devices, you can join **Sony**, **Nokia**, **Huawei** and others in lending me anything from Android 6.0.1 or later to independently test. This is a free service, devices can be returned within a week or so. Use my [contact](/contact/) page to get in touch or [email me directly](mailto:jason@bayton.org).
+I welcome additional devices for testing! If you’re an **OEM** or **reseller** of Android devices, you can join **Sony**, **Nokia**, **Huawei**, **Lenovo** and others in lending me anything from Android 6.0.1 or later to independently test. This is a free service, devices can be returned within a week or so. Use my [contact](/contact/) page to get in touch or [email me directly](mailto:jason@bayton.org).
 
 For more information on what’s involved in testing, please head to: [Android Enterprise independent validation process and information](/android/android-enterprise-device-support/validation-process-and-information/).
 
 </div>
 
-Advanced testing
-----------------
+## Example reports
 
-The following devices have undergone advanced testing. Introduced in June 2019, advanced testing follows the same [process](/android/android-enterprise-device-support/validation-process-and-information/) as standard testing, but each individual restriction/function is documented and verified irrespective of outcome across at least two EMMs.
+The following devices have undergone advanced testing. Introduced in June 2019, advanced testing follows the [process highlighted here](/android/android-enterprise-device-support/validation-process-and-information/), with each individual restriction/function documented and verified irrespective of outcome across at least two EMMs.
 
 A report containing 700+ touch points is provided to the OEM on completion along with any recommendations.
 
 - [Google Pixel 3a Android Enterprise validation report](/android/android-enterprise-device-support/google-pixel-3a-validation-report/)
 - [Moto G7 Power Android Enterprise validation report](/android/android-enterprise-device-support/moto-g7-power-android-enterprise-validation-report/)
-- [Sony Xperia L3 Android Enterprise validation report](/android/android-enterprise-device-support/sony-xperia-l3-android-enterprise-validation-report/)
-
-## Standard testing
-
-Previously listed devices here have been removed. Refer to the advanced tested devices to understand the testing undertaken in validating AE compatibility, and if interested you may [contact me](/contact) to discuss testing your Android device at no cost.
+- [Sony Xperia L3 Android Enterprise validation report](/android/android-enterprise-device-support/sony-xperia-l3-android-enterprise-validation-report/)

_src/android/android-enterprise-device-support/validation-process-and-information.md

@@ -16,13 +16,6 @@ discourse_permalink:
 FeaturedBackground:
     - android
 ---
-<div class="callout callout-warning">
-
-### No longer updated
-
-**While I am still actively testing devices**, I no longer publish them here. Consider the below to be historical, and not to be taken as current status of a device. If you’d like your devices tested against Android Enterprise functionality, feel free to get in touch. 
-
-</div>
 
 <div class="callout callout-info">
 
@@ -38,24 +31,16 @@ If you’re interested in knowing more about the project as a whole and the back
 
 In order to validate the implementation of Android Enterprise on a device, I undertake the following:
 
-- Attempt to perform an NFC-bump using a provisioning application supplied by either [MobileIron](https://play.google.com/store/apps/details?id=com.mobileiron.client.android.nfcprovisioner) or [AirWatch](https://play.google.com/store/apps/details?id=com.airwatch.relay) (normally both).
-- Attempt to perform a QR scan based on codes generated [manually](/docs/enterprise-mobility/mobileiron/manual-android-enterprise-work-managed-qr-code-generation-for-mobileiron/) ([WS1 source](https://my.air-watch.com/help/9.1/en/Content/Platform_Guides/Android_Work/C/Enrollment_Overview.htm)) or [automatically](https://play.google.com/store/apps/details?id=com.mobileiron.client.android.nfcprovisioner).
-- Attempt to enrol using the DPC identifier in the Google account prompt, normally *afw#mobileiron.core*, *afw#mobileiron.cloud* or *afw#hub*.
-- Attempt to enrol using a GSuite address and the Google [Device Policy Management](https://play.google.com/store/apps/details?id=com.google.android.apps.enterprise.dmagent) DPC.
+- Attempt to perform an NFC-bump using a provisioning application supplied by EMM vendors where available, or through a NFC tag with a custom payload where not.
+- Attempt to perform a QR scan based on codes generated [manually](/docs/enterprise-mobility/mobileiron/manual-android-enterprise-work-managed-qr-code-generation-for-mobileiron/) or automatically through a supported EMM.
+- Attempt to enrol using the DPC identifier in the Google account prompt, normally *afw#mobileiron.core*, *afw#mobileiron.cloud*, _afw#setup_ or *afw#hub*.
+- Attempt to enrol using a Google Workspace address with or without the Google [Device Policy Management](https://play.google.com/store/apps/details?id=com.google.android.apps.enterprise.dmagent) DPC.
 - Utilise any of the above provisioning methods to deploy a COSU (kiosk) environment.
 - Utilise any of the above provisioning methods to deploy a Fully managed work profile (COPE) environment.
 - Attempt to enrol into an EMM after normal setup to generate a work profile.
 - If supported, attempt to enrol using zero-touch provisioning.
 
-The above provisioning tasks (with the exception of the GSuite enrolment currently) are documented here: [Android Enterprise provisioning guides](/android/android-enterprise-provisioning-guides/). Testing may be completed on EMM platforms other than those mentioned above for any task at any time.
-
-### EMM configuration files
-
-Should you wish to see first-hand the policies/configs/profiles utilised to validate devices against (security, restrictions, firmware), feel free to import the following into your own EMM platform:
-
-#### MobileIron Core
-
-[MobileIron Policies](https://cdn.bayton.org/uploads/2019/01/MI_AEvalidation.zip)[Download](https://cdn.bayton.org/uploads/2019/01/MI_AEvalidation.zip)
+The above provisioning tasks (with the exception of the Google Workspace enrolment currently) are documented here: [Android Enterprise provisioning guides](/android/android-enterprise-provisioning-guides/). Testing may be completed on EMM platforms other than those mentioned above for any task at any time.
 
 ### Success criteria