| 15 Aug 2021 |
 pie_ | if yall're willing to provide guidance i can bring it up at the SoN team meeting tomorrow, though i still have a project i havent finished | 23:29:11 |
 danielrf | samueldr: something like that, I just know that each new device comes with a bunch more modules than before--but I'm not sure when the switch over to GKI will be "complete" | 23:29:18 |
| danielrf | I haven't followed it too closely | 23:29:26 |
| pie_ | im not entirely afraid of kernel dev but i certainly dont have much experience with it | 23:29:49 |
 samueldr | my experience with GKI is that it's making OEM not provide all the modules source code, sometimes at all, sometimes in usable manner | 23:30:14 |
| danielrf | pie_: So there's two things here: 1) build kernels for generic emulation devices (and potentially switch the way we build kernels) and 2) build the android automotive emulator (https://source.android.com/devices/automotive/start/avd/android_virtual_device) | 23:30:59 |
| danielrf | those are hopefully two independent tasks | 23:31:44 |
| pie_ | what have i gotten myself into | 23:31:50 |
| danielrf | pie_: :D | 23:32:08 |
| danielrf | Ah, here's some automotive-specific instructions for the kernel: https://source.android.com/devices/automotive/start/avd/android_virtual_device#build-an-avd-kernel | 23:33:02 |
| pie_ | the question is really how dependent the bluetooth passthrough is on the automotice | 23:43:14 |
| pie_ | ´´´
AVD kernels are similar to other Android kernels in that all are pre-built images. Normally, you can use the standard goldfish kernel pre-built images as is from each Android release.
To experiment with kernel changes:
´´´ | 23:43:53 |
| pie_ | oh good | 23:43:54 |
| 16 Aug 2021 |
| pie_ | danielrf: how do/did you iterate with 10 hour build timeS? | 00:23:01 |
| danielrf | pie_: at the rate of 1-2 builds per day haha | 00:26:50 |
| danielrf | it was painful | 00:26:52 |
| pie_ | i had that with a much smaller project x) | 00:27:09 |
| samueldr | when I was toying with robotnix it was a one try per evening thing | 00:27:27 |
| samueldr | though funnily enough my last two contributions take far less time | 00:27:48 |
| samueldr | (TWRP, anbox) | 00:27:57 |
| danielrf | samueldr: btw, I'm currently working on building waydroid | 00:28:59 |
| samueldr | neat | 00:29:05 |
| samueldr | last I looked I couldn't find it lol | 00:29:12 |
| danielrf | I haven't looked into the host-side at all yet, but just wanted to see if I could get the guest to build in robotnix | 00:29:22 |
| samueldr | though the not-neat part is AFAIUI it totally won't work on X11 :( | 00:29:24 |
| samueldr | and something I'm not sure about, whether it will work with hardware without accelerated graphics | 00:29:56 |
| pie_ | at the cost of some flexibility apparently i could just use androids build in "hci snoop" functionaity | 01:58:43 |
| pie_ | * at the cost of some flexibility apparently i could just use androids built in "hci snoop" functionaity | 01:58:51 |
 philipp | Ooooh! I am very interested in waydroid, pretty much exactly what I was looking for but the decided to just go classic qemu virtualisation for the time being. | 09:48:57 |
| 17 Aug 2021 |
| pie_ | danielrf: are you willing to maybe make some issues on the issue tracker that i can point the summer of nix people at for thngs id like to work on? | 09:03:20 |
