| 9 Aug 2023 |
 @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 |
