| 9 Aug 2023 |
 atemu12 | Device Tree is part of the kernel | 11:02:20 |
 @angryant:envs.net | Ah. It was just weirdly called out separately in the repo description. | 11:02:42 |
| atemu12 | I'm not too knowledgable about that but AFAIK ARM devices don't have standardised device discovery via PCIe and the like, so you need to declare where which device is upfront | 11:02:52 |
| atemu12 | This bus is where x is, this memory range is mapped to device y and so on | 11:03:26 |
| atemu12 | If someone has ported Android to your device (and open sourced that), you could build that using Robotnix | 11:04:11 |
| 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 |
| atemu12 | I can highly recommend taking a look at Fairphone | 11:18:19 |
| @angryant:envs.net | I did - they're basically the second choice. | 11:18:36 |
| atemu12 | That will also be a solution to the phone falling apart in another 7 years ;) | 11:18:39 |
| atemu12 | Given that the search for an unofficial LOS port revealed Nothing, I wouldn't buy that phone. Even without robotnix, you'd be stuck with the vendor rom | 11:24:37 |
| atemu12 | Given that's it's been a year since release and that the last NothingOS release was 3 months ago, it seems it's already dead | 11:25:09 |
| atemu12 | Fairphone has a history of great LOS support and one of the core maintainer has an FP4 apparently: https://forum.xda-developers.com/t/rom-13-official-lineageos-20-for-fairphone-4.4536035/ | 11:26:03 |
| @angryant:envs.net | Came across Paranoid Android. If I understood correctly, using that with robotnix "just" involves updating robotnix to also support the fetch & build of this rom as documented in its repositories? https://github.com/AOSPA | 14:20:51 |
| atemu12 | AngryAnt: Supporting a new flavour often is a bit more involved because they tend to have their own peculiarities | 15:29:57 |
| atemu12 | Not familiar with pandroid tho | 15:30:05 |
 samueldr | if they're a lineageos derivative (which many custom roms actually are) it may be enough | 17:26:39 |
| samueldr | but only "try it and see" will tell | 17:26:44 |
| samueldr | you would start from the lineageos flavour rather than aosp | 17:27:01 |
| 10 Aug 2023 |
| @angryant:envs.net | Primary interest in looking into it is aosp does actually support the nothing phone. | 07:55:47 |
