Just did my first build and it worked fairly well (development branches). Hopefully the detail below help more than being annoying. It went surprisingly smooth, unlike compiling OpenWRT, except for one thing. I was a bit confused about signing and generating the certificates (I tried to explore the options); I will recompile after repo diff/ syncing and removing all the changes that I may or may not have done while trying to understand what I was doing. I was able to flash my phone with no issue. And I did made sure that the automated update were disabled as per the warning in the instruction.

My setup is a debian 12 vm using virsh with no graphics installed. What I did was (after following the instructions specific for Debian 12 and yarnpkg) to download repo from Google (manual method) and the required packages listed in "Install required software". Then for adevtool I followed the instruction from (what I hope is the) official github page. Since it mentioned minimum I installed node.js 22 using npm.

The repo tool and the .jar file from adevtool were all installed in the bin directory that I created in the home directory (~/bin). I then exported the path and added it to .bashrc . That's it. That and I found that I needed to restart from the beginning with lunch command if I were to exit the current session.

https://source.android.com/docs/setup/start/requirements
https://github.com/kdrag0n/adevtool/tree/main

And with this setup (no windows involved) I also saw the HOST_CROSS_OS=windows .

I am using ubuntu server on cloud computing , so it's not related to that as I have been using this server for 2 years now , ( 5 years of aosp experience here)

I was building fine gOS android 14

Then I am the only N00b here. And to correct myself I was better off using yarnpkg to install adevtool because I couldn't repeat what I just did. I tried before with a gui and the whole android studio installed (and some more) and I was stuck in a loop of error or missing packages that I couldn't understand. I thought that maybe you were in a similar situation.

eagle13 updates ?

I think it's possible that you are not getting replies that move you forward because the questions you are posting do not contain sufficient detail for the readers of the thread to guess what might be going wrong.

Given the number of people who are successfully building GrapheneOS, I suspect that whichever issue(s) you are running into are somehow specific to your setup. Without access to your setup I suspect people here aren't going to be able to help diagnose what is going wrong with it.

Two things you might try:

  • The developer chat room on Matrix/Discord/etc.
  • Starting over, i.e., downloading the GrapheneOS sources from scratch using repo, etc., and trying to build that.
      2 months later

      GOS team: seriously ? it is still presistant and no fix ? How do you build there ? Maybe need to update the build guide?

      • de0u replied to this.

        • Dde0u

          • Post #27

          eagle13 Can you report on which things suggested in the previous post (de0u) have been tried?

              new build env , old build env , sync the source code again , tried with both oriole and panther devices .. gone through the files to try to fix the path ... it is just not working

              6 days later

              updates?

              • de0u replied to this.

                • Dde0u

                  • Post #30
                  • Edited

                  eagle13 I just successfully built bluejay-cur-userdebug using tag 2024123000 on vanilla Ubuntu 22.04.

                  The only thing that was a bit of a detour was that I had to install yarn via npm because I couldn't figure out how to convince apt to install packages (such as yarnpkg) on top of a Node installed from Node's repository.

                  Looking back at your earlier post, I'm not sure where "aosp_oriole" is coming from, as in lunch aosp_oriole-ap2a-userdebug. I am not seeing that in the GrapheneOS build directions.