In reply to @atemu12:matrix.org
I might be getting ajs124 ' old Pixel 4a soon though at which point I could

In reply to @jaen:matrix.org
Okay, pushed one more commit — patching derivation won't work, because it's just a shim apparently and it downloads it's code from the interwebs anyway. I did leave overlaying pkgs to a matching version, though (not sure if it matters, but why not). Other than that removed python2 from a couple of places that seemed safe and switched flake-compat to the nix-community version. Let me know if you can test this works for you and/or you have any other remarks. I tried to build some lineageos myself and at least it fetched the code and started building the ROM. It failed when trying to build Chromium, but I guess that's fare enough for it to not be related — would appreciate a double–check, though.

Hmmm, doesn't Vanadium need that, though? As far as I can see there are no binaries available. So unsure if it's removable if we want to keep GrapheneOS? Thought that's a separate topic I guess, for now I just want to see if any ROM will build on my PR, currently running this to see if it builds:

nix-build --arg configuration '{ device="lemonade"; flavor="lineageos"; androidVersion=13; apps.chromium.enable = false; webview.prebuilt.enable = false; webview.chromium.enable = false; webview.chromium.availableByDefault = false; }' -A factoryImg

Don't have an appropriate phone to test it on, though. If there's anything else I should test or you can test it at least for the things you use and should know work — let me know.

In reply to @atemu12:matrix.org
As for repo, is it really not possible to run it without it attempting to download some other version? I'd prefer to patch it to not download any updates whatsoever

Ok, got three basic checks (running nix flake check on flake/templated flake, formatters/linters and pytest) working again — https://github.com/jaen/robotnix/actions/runs/9243699871. Will see if I can get more working, but at least it's something. Two questions re: that:

• pre-commit hooks yay/nay? When doing those changes I certainly forgot to re–format code once or twice — GHA caught that, but maybe it would be better to have caught that before pushing?
• I've noticed after adding treefmt-nix and nix-github-actions get propagated down to the client flake as dependencies when running the templated flake test. Do you think it would make sense to try a pattern like https://figsoda.github.io/posts/2023/developing-nix-libraries-with-subflakes/ to avoid it?

I've been trying to get LineageOS 21 to build (discussed here) , and feel like I'm getting close. Updated the python scripts, device and vendor files, and patches. Now when I build I'm running into the following. Not sure where to make a change to address this:

warning: Git tree '/home/erahhal/Code/nix-android' is dirty
warning: creating lock file '/home/erahhal/Code/nix-android/flake.lock'
warning: Git tree '/home/erahhal/Code/nix-android' is dirty
these 3 derivations will be built:
  /nix/store/jp9lghipjq8gym5i4i37i9q7scc8wqlp-robotnix-lineage_cheetah-2024052404.drv
  /nix/store/lmq73sjh1kk0dpfqqhrqkky4cvg7vd0j-ota-tools.drv
  /nix/store/k38ncc9ih0523fsisrm4wcmrwx67diap-cheetah-ota_update-2024052404.zip.drv
robotnix-lineage_cheetah> building '/nix/store/jp9lghipjq8gym5i4i37i9q7scc8wqlp-robotnix-lineage_cheetah-2024052404.drv'
robotnix-lineage_cheetah> unpacking sources
robotnix-lineage_cheetah> patching sources
robotnix-lineage_cheetah> building
robotnix-lineage_cheetah> Build type choices are:
robotnix-lineage_cheetah>      1. release
robotnix-lineage_cheetah>      2. debug
robotnix-lineage_cheetah>
robotnix-lineage_cheetah> Which would you like? [1] release
robotnix-lineage_cheetah> In file included from build/make/core/config.mk:389:
robotnix-lineage_cheetah> In file included from build/make/core/envsetup.mk:51:
robotnix-lineage_cheetah> build/make/core/release_config.mk:100: error: No release config set for target; please set TARGET_RELEASE, or if building on the command line use 'lunch <target>-<release>-<build_type>', where release is one of: ap1a.
robotnix-lineage_cheetah> 00:43:28 dumpvars failed with: exit status 1
error: builder for '/nix/store/jp9lghipjq8gym5i4i37i9q7scc8wqlp-robotnix-lineage_cheetah-2024052404.drv' failed with exit code 1;
       last 10 log lines:
       > building
       > Build type choices are:
       >      1. release
       >      2. debug
       >
       > Which would you like? [1] release
       > In file included from build/make/core/config.mk:389:
       > In file included from build/make/core/envsetup.mk:51:
       > build/make/core/release_config.mk:100: error: No release config set for target; please set TARGET_RELEASE, or if building on the command line use 'lunch <target>-<release>-<build_type>', where release is one of: ap1a.
       > 00:43:28 dumpvars failed with: exit status 1
       For full logs, run 'nix log /nix/store/jp9lghipjq8gym5i4i37i9q7scc8wqlp-robotnix-lineage_cheetah-2024052404.drv'.
error: 1 dependencies of derivation '/nix/store/k38ncc9ih0523fsisrm4wcmrwx67diap-cheetah-ota_update-2024052404.zip.drv' failed to build
┏━ 1 Errors:
┃ error: builder for '/nix/store/jp9lghipjq8gym5i4i37i9q7scc8wqlp-robotnix-lineage_cheetah-2024052404.drv' failed with exit code 1;
┃        last 10 log lines:
┃        > building
┃        > Build type choices are:
┃        >      1. release
┃        >      2. debug
┃        >
┃        > Which would you like? [1] release
┃        > In file included from build/make/core/config.mk:389:
┃        > In file included from build/make/core/envsetup.mk:51:
┃        > build/make/core/release_config.mk:100: error: No release config set for target; please set TARGET_RELEASE, or if building on the command line use 'lunch <target…
┃        > 00:43:28 dumpvars failed with: exit status 1
┃        For full logs, run 'nix log /nix/store/jp9lghipjq8gym5i4i37i9q7scc8wqlp-robotnix-lineage_cheetah-2024052404.drv'.