You can just follow the official build instructions with a single change: when specifying the build target, change it from -user to -userdebug:

https://grapheneos.org/build#setting-up-the-os-build-environ...

▲

imiric 4 days ago | parent [-]

Hhmm that seems like a hassle, TBH.

One of the things I like the most about GOS is the web installer, and how easy it is to use. If I need a custom build, to run my own server, and sacrifice performance for it, it doesn't seem worth it. It would also be good to know what a debug build entails, how exactly it is "less secure", and so on. Since this is unlikely to be documented by the GOS team, a 3rd party guide would still be helpful.

	▲	3abiton 4 days ago \| parent \| next [-]
		> It would also be good to know what a debug build entails, how exactly it is "less secure". Using software engineering terms, think of the official GOS as production release, and the debug version as test release. You deploy it by actiually building it, like building a linux kernel. This takes lots of reaources (RAM + storage). But also is quite flexible because you can compile and build it whenver there is a new update. And you can sign the build yourself. The reason why they say it's insecure is the same why your server sysadmin does not give you the root password. You can do some serious damage if you have no idea what you're doing. On Android, root allow you to peek on other processes and apps, so if you grant root to a malicious app, high risk of data leakage. That's it though. Been rooting and building roms since early android days, no issues for me as I tend to use open source tools most of the time.
	▲	j4hdufd8 4 days ago \| parent \| prev [-]
		This is well documented in AOSP, what do you mean?