| 14 Aug 2021 |
 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 |
| pie_ | if someone throws hardware at me and is willing to help or something, I can try to make an "enable bluetooth in the emulator with a dongle" module | 23:08:37 |
| danielrf | pie_: unfortunately I don't have any experience with android auto (either in the emulator or on real cars) | 23:08:44 |
| pie_ | is it significantly different | 23:08:58 |
| danielrf | pie_: Yeah, those instructions could potentially be turned into a robotnix module | 23:08:59 |
| danielrf | but that could help people after you--blazing the trail is the hard part :) | 23:09:23 |
| pie_ | this could be a major capability given that it doesnt seem to be widely supported | 23:10:01 |
| pie_ | (i dont know if thats because google doesnt want people to know about it?) | 23:10:19 |
| pie_ | In reply to @danielrf:matrix.org
but that could help people after you--blazing the trail is the hard part :) well yes but RE: there is no way i can build this unless someone throws a shell at me | 23:10:44 |
| pie_ | In reply to @jcie74:matrix.org
(i dont know if thats because google doesnt want people to know about it?) maybe best if we dont advertise too hard heh :PP | 23:11:07 |
| pie_ | In reply to @danielrf:matrix.org
pie_: unfortunately I don't have any experience with android auto (either in the emulator or on real cars) the fact that its "automotive" if thats different from the normal distro,is both worrying, and id hope it doesnt matter, usb passthrough should be pretty standard right ._. | 23:11:56 |
