• General

  • Replacing GOS boot animation with vanilla AOSP boot animation

DeletedUser130 It is already obvious to anyone the device is running GrapheneOS, as Pixel tells anyone booting it up that the device is loading an alternate operating system, with Graphene's public key. This behavior cannot be modified.

    DeletedUser130 They will most likely not

    "Otherwise it would continue to be immediately obvious that a device is using GOS when it boots."

    That is the point of a boot animation, yes. Same with the key hash that flashes when you start the device, and im sure you could query that info using adb

      DeletedUser130 Otherwise it would continue to be immediately obvious that a device is using GOS when it boots.

      I hope so. It's in the nature of things that this is the case.

        itsjpb
        you could of course make your own fork

        No. This is not what this thread is about. And it's also not the first thing that should be suggested when someone suggests something for an open source project.

        itsjpb
        a simple search would show this has been discussed before. here is a thread where moderators discuss why it's unlikely to change.

        The title and first post of that other thread is asking something completely different. It's essentially asking to remove the remaining stock branding from the boot sequence, which is essentially the complete opposite of what this thread here is suggesting.

        But since that other thread later became off-topic and was used to discuss the removal of the GOS boot animation and since the @GrapheneOS team had already replied on that other thread, the conversation can also continue there: https://discuss.grapheneos.org/d/4335-remove-your-phone-is-loading-different-os-remove-google-logo-in-startup/31

        • de0u replied to this.

              DeletedUser130 itsjpb
              you could of course make your own fork

              DeletedUser130 No. This is not what this thread is about. And it's also not the first thing that should be suggested when someone suggests something for an open source project.

              I think the fork suggestion was the second suggestion, with the first suggestion being that an official project account had indicated that the project is unlikely to make the requested change.

              Helpfully pointing out the option of forking when the suggested something has previously been suggested and rejected is not the same thing as telling anybody suggesting anything to fork.