| 13 Aug 2021 |
 khimaros | which robotnix build is best for running on sailfish? | 19:33:03 |
|  Linux Hackerman joined the room. | 20:59:37 |
|  cde removed their profile picture. | 21:16:10 |
| cde set a profile picture. | 21:16:46 |
| 14 Aug 2021 |
 jack | In reply to @khimaros:matrix.org
which robotnix build is best for running on sailfish? I've had good luck with the google hardware and the GrapheneOS tag on pixel 2xl and pixel 5.
Except that time I locked the bootloader with the wrong keys, but that was just me being dumb. | 00:47:30 |
| khimaros | jack: on sailfish specifically? i thought grapheneos dropped support for the original pixel? | 00:48:15 |
|  volfyd joined the room. | 02:34:41 |
| volfyd | Hi. Does anyone have any tips about getting ccache to work? I have never used Nix before. I followed the instructions and added ccache.enable = true; to my .mix config file and I'm running with --option extra-sandbox-paths "/path/to/keys /var/cache/ccache" and I'm [54985/96665] the way through building chromium but no files appear in /var/cache/ccache even though it is group nixbld and mode 770 | 02:38:46 |
 danielrf | volfyd: The ccache support is only for the main AOSP build system. It does not work for chromium and its derivatives | 04:23:03 |
| danielrf | khimaros: I'd probably go with lineageos for marlin/sailfish. There is support for marlin/sailfish in the vanilla flavor, but it's only up to Android 10, and hasn't been updated since Google stopped pushing updates for it | 04:24:22 |
| danielrf | volfyd: If you're trying to save build time and are willing to use prebuilt versions of the kernel / browsers, I do provide a "Nix binary cache" for those: https://docs.robotnix.org/building.html#binary-cache | 04:27:22 |
| volfyd | danielrf ah thanks. I had it in my mind that your cache wouldn't help me since you aren't compiling for my device but I guess the cache might work for apks. | 05:28:33 |
 philipp | What lineage device would you reccomend to use for emulation on a x86_64 CPU? | 19:12:26 |
| danielrf | Redacted or Malformed Event | 21:57:23 |
| danielrf | philipp: Use device = "x86_64"; | 21:57:38 |
| danielrf | That's the "generic" x86_64 device | 21:57:51 |
| philipp | Ah, yes! That's what I was looking for. Thank you very much! | 22:10:45 |
| 15 Aug 2021 |
| danielrf | Pushed grapheneos-2021081411. Tested on crosshatch. | 03:05:38 |
| danielrf | Periods were removed from the BUILD_NUMBER (and consequently, tag as well), following upstream's change in naming convention. Certain apps assumed the BUILD_NUMBER was actually a number | 03:06:15 |
 pie_ | this looks rather complicated https://source.android.com/devices/automotive/start/passthrough | 22:56:19 |
| pie_ | can robotnix help me with the bluetooth stuff? | 22:56:27 |
| pie_ | Im open to better ideas, basically i want to sniff some bel | 22:57:12 |
| pie_ | * Im open to better ideas, basically i want to sniff some BLE | 22:57:14 |
| pie_ | also do I remember correctly that robotnix needs like 100 gigs to build or something? | 23:04:51 |
| pie_ | Ive never actually used it | 23:04:55 |
| pie_ | "The AOSP project recommends at least 250GB free disk space as well as 16GB RAM" holy shit | 23:05:35 |
| danielrf | I think 100GB is closer to the real number than 250GB, but it's good to still have some margin | 23:06:44 |
| danielrf | and IIRC the latest version is now starting to push beyond >16GB unfortunately. (definitely it is for the kernel) | 23:07:19 |
| pie_ | even if i ask someone if i can build with their hardware idek how i can reasonably do this | 23:07:29 |
| danielrf | using zram can help | 23:07:35 |
