Remove your phone is loading different os + remove google logo in startup

de0u

DeletedUser130 Clothing can be put on and off. Wearing it is an optional choice. Which means it's not comparable to a boot animation.

Running GrapheneOS is a choice. Running stock GrapheneOS, as opposed to a personal build, is also a choice.

yore

DeletedUser130 But probably not by rebooting a phone and holding up the phone during boot every single time.

That's the solution right there: assuming you're being targeted, cover your screen if you're rebooting your phone in public. Or avoid rebooting until you're in private.

These are really your only best solutions here. You're free to create a custom build that does not show the GrapheneOS splash screen if you have the time and knowledge to do so and modify it to your liking. It still won't hide the warning screen that clearly shows the phone is running a different OS.

Besides that, I think this discussion is only going in circles.

other8026

I don't see any point in engaging any further. I understand that people have their opinions and aren't going to change their minds. I can respect that.

Please see the reply from the project account here. I don't think anything that has been said since their reply will make them rethink their changes.

DeletedUser130

other8026

Please see the reply from the project account here.

That initial reply did not consider that the GOS logo in the boot animation can also be used to identify GOS devices without having direct physical access, by simply looking at it from afar. The verified boot key hash that is being displayed during boot on the other hand typically can not simply be looked at / be identified from afar, as that is too small and too long to easily read, even at regular viewing distances.

other8026

I don't think anything that has been said since their reply will make them rethink their changes.

Instead of assuming what @GrapheneOS would or wouldn't think, maybe it would be better to simply let @GrapheneOS reply.

Xtreix

DeletedUser130 The vanilla AOSP boot animation is not similar to the Pixel stock OS boot animation, it's completely different.

The vanilla AOSP boot animation does not show a Google logo.

The vanilla AOSP boot animation shows an Android logo. Which is visible from the following (random) video for example (starting at around 38 seconds): https://www.youtube.com/watch?v=E9KeTHc5I6Y&t=35s

GrapheneOS is not AOSP, the logo at the boot animation must be correct for the official versions to avoid any confusion, as other members have already explained, hide your screen in public when the device starts up or build GrapheneOS yourself if you have the skills.

other8026

GrapheneOS developers don't make decisions or changes without discussing them first. They weigh pros and cons before doing anything. They're fully aware of the very obvious fact that the boot animation is more visible than the boot key hash. I'm not sure why you're presenting this fact as if nobody could have possibly considered it before you mentioned it.

You're ignoring the very obvious "loading another OS" screen that is displayed immediately before the boot animation and you're assuming that that + a generic AOSP boot animation won't get the same attention as "loading another OS" + GrapheneOS boot animation will.

A project member using the official GrapheneOS account has already said "There's no point in changing this" and they're not going to change something because one person is arguing nonstop in favor of a change. They may very well post more here, but for now I'm locking this discussion because arguing in circles is not productive.

« Previous Page