Dear Daniel & dev team,

I own 2 phones. Both are the same model - Samsung Galaxy A32 5G (SM-A326), with initial Android ver. 11. The first is intact and has genuine OS. The second may be potentially tampered. It would be very interesting and useful to check the OS integrity/authenticity of the second phone using Auditor. Unfortunately the model is not in the device support list.

Are there any chances that it will be added to supported models?
I've already submitted key attestation sample as per https://attestation.app/tutorial#expanding-device-support using the first phone.
Is there anything I can do to assist you further?

Thank you for your work and creation of unique products.

PS. BTW, after Android was updated from 12 to 13 and Auditor from 67 to 68, any attempt to submit sample data returns "Failed to submit sample data. java.io.IOException: response code: 413" error and the phone keeps notifying about this error until the forced stop of the app.

    Eugene Hi there.

    The Auditor app is only for attestation of GrapheneOS. Not any other OS. It can't perform attestation of the OS running on your Samsung Galaxy.

      treequell This page seems to discuss validating non-GrapheneOS installs on devices I don't think GrapheneOS has run on. Am I misunderstanding it?

        de0u Attestation requires two devices.

        • The auditor: the device running GrapheneOS,
        • The auditee: another device you use to verify that the auditor is running GrapheneOS.

        Many Android devices can be used as the auditee, as shown in that link.

        treequell That is incorrect. Please look at: https://attestation.app/about#device-support

        If a device launched with Android 8, it can be verified by Auditor if it's running the Stock OS, provided that Auditor adds explicit support for said model.

        As far a device doing the auditing, any device running Android 8 or later will do just fine, not just the ones listed there.

        It can also of course verify GrapheneOS (in addition to Stock OS) for the devices that GrapheneOS supports.

        With all of that said, @de0u - this issue may provide some clarity and insight into why more devices are not being added at the moment:

        https://github.com/GrapheneOS/Auditor/pull/189

        TL;DR is that to my understanding it's too complex and time consuming to do on a large scale as things currently stand. A new approach is needed and elaborated on a little bit in the issue above.

          matchboxbananasynergy With all of that said, @de0u - this issue may provide some clarity and insight into why more devices are not being added at the moment:

          https://github.com/GrapheneOS/Auditor/pull/189

          Ok, now my understanding is that in theory Auditor can handle lots of devices but in practice there is a workflow impediment to supporting lots of them.

          Or, "In theory there is no difference between theory and practice, while in practice there is. --Benjamin Brewster (1882)".