the play services are not installed by default*

just so everyone is aware grapheneos only support’s pixels because it is specifically designed for taking advantage of the hardware security features found in google’s tensor and titan chips. and thus installing it on another phone would kinda miss the point (and vastly increase the scope of the project)

google is also basically the best company when it comes to phones for custom roms, as they provide stock images, a simple bootloader unlocking process (that doesn’t void your warranty as far as i can tell), and generally the aosp and software support that comes from being the phone of the developer of android.

I’m curious why you want an intel cpu over an amd one

Well yes obviously but it does serve a purpose as a maintained fork, that’s why I included that. I expect a normal fork will be made soon because of this news.

The readme states:

“This repo also serves as an updated version of the original neofetch since the upstream dylanaraps/neofetch doesn’t seem to be maintained anymore (as of Oct 27, 2023, the original repo hasn’t merged a pull request for almost 2 years). If you only want to use the updated neofetch without pride flags, you can use the neofetch script from this repo. To prevent command name conflict, I call it neowofetch :)”