| 15 Aug 2021 |
 pie_ | i can just reverse engineer the app probabyl but this is a good exercise i thnk | 23:14:09 |
| pie_ | i go at things from multiple directions | 23:14:15 |
| pie_ | decompiled code is "dead" | 23:14:29 |
| pie_ | looking at a real live capture might also be easier (or not) | 23:15:39 |
| pie_ | i supose i could also poke stuff via Xposed or something | 23:15:55 |
| pie_ | the pipe dream is to write some foss firmware | 23:16:11 |
| pie_ | so it could be good for testing for compatibility i guess | 23:16:33 |
| pie_ | generally sounds nicer to deal with the emulator than the phone but idk | 23:16:48 |
 danielrf | yeah this definitely looks nontrivial | 23:20:31 |
| danielrf | Even the first step https://source.android.com/devices/automotive/start/passthrough#bt-guest-kernel to add a kernel module is nontrivial because we're just using the prebuilt goldfish kernel for the emulator currently | 23:21:12 |
 samueldr | pie_: looking at the PRs I made to add support for additional flavours may help
https://github.com/danielfullmer/robotnix/pulls?q=is%3Apr+author%3Asamueldr | 23:21:24 |
| danielrf | not immediately sure how/where to modify that | 23:21:25 |
| pie_ | danielrf: i think getting something like https://source.android.com/devices/automotive/start/avd/cloud_emulator low key set up would also be very interesting | 23:21:49 |
| samueldr | (here thinking solely about the flavour) | 23:21:49 |
| pie_ | In reply to @danielrf:matrix.org
Even the first step https://source.android.com/devices/automotive/start/passthrough#bt-guest-kernel to add a kernel module is nontrivial because we're just using the prebuilt goldfish kernel for the emulator currently oh no | 23:22:11 |
| pie_ | so the kernel rebuilds arent automated? | 23:22:25 |
| pie_ | i mean, i have to replicate the upstream build process and feed robotnix a blob or something? | 23:22:54 |
| danielrf | not for emulator builds--we only build kernels for devices currently | 23:22:59 |
| pie_ | "how hard could it be" | 23:23:12 |
| danielrf | In reply to @jcie74:matrix.org
i mean, i have to replicate the upstream build process and feed robotnix a blob or something? or write some nix expressions to do this in an integrated way | 23:23:22 |
| pie_ | id probably need guidance on that | 23:23:36 |
| samueldr | huh, they run android auto on pixel xl devices?
https://source.android.com/devices/automotive/start/pixelxl | 23:23:36 |
| pie_ | btw i can probably argue for working on this stuff in scope of summer of nix but i dont know how much i could actually get done | 23:24:07 |
| danielrf | In reply to @samueldr:matrix.org
huh, they run android auto on pixel xl devices?
https://source.android.com/devices/automotive/start/pixelxl That's be interesting to try out if my pixel 3 xl wasn't my daily driver! :) | 23:24:52 |
| pie_ | i imagine the kernel is deep enough in the build tree that rebuilding that basically causes a full rebuild? | 23:25:48 |
| samueldr | wondering if unsupported devices can still run it | 23:25:52 |
| samueldr | for those that can run QQ3A.whatever | 23:26:12 |
| danielrf | I'd expect any of the devices here might work: https://android.googlesource.com/device/google_car/+/refs/heads/master | 23:26:21 |
| danielrf | pie_: kernels are built separately from the main android build system | 23:26:37 |
| pie_ | samueldr: i get the impression that everything is unsupported but you are allowed to make it work yourselfd :P | 23:26:39 |
