| 9 Aug 2023 |
 atemu12 | Again, Robotnix "just" runs the AOSP build inside a Nix sandbox; the AOSP build still needs to work in general | 11:05:29 |
| atemu12 | We can then inject custom kernels, µG, F-droid or custom webviews into that build process in a somewhat generic way | 11:06:07 |
 @angryant:envs.net | Cool. Thanks for the overview :) My knowledge of android is quite limited and I clearly made some Linux assumptions about it. Looks like there's some unofficial progress on Lineage on the Nothing phone, so it seems promising that eventually a robotnix path will be available :) | 11:10:43 |
| @angryant:envs.net | Realising that at present Lineage support in robotnix is experimental. | 11:11:12 |
| atemu12 | AngryAnt: If there's a LOS port already (check github), trying that out could prove to be rather trivial | 11:11:28 |
| atemu12 | Even if it's experimental | 11:11:39 |
| atemu12 | That "just" means not everything might be working | 11:11:50 |
| atemu12 | As for LOS support in Robotnix, I think that's about the only "maintained" part right now | 11:12:26 |
|  @gsaurel:laas.fr left the room. | 11:12:35 |
| atemu12 | I'm currently cooking up a LOS bump | 11:12:37 |
| @angryant:envs.net | Ah nice | 11:15:18 |
| @angryant:envs.net | I'm basically looking at replacing a daily driver phone falling apart after seven years constant use and would like something which, among other things, could potentially be compatible with a robotnix flow. The Nothing phone ticks all my goals - with the robotnix flow being the only question mark. | 11:17:56 |
