| 9 Aug 2023 |
 atemu12 | And has no real relation to robtonix | 10:54:38 |
| atemu12 | That's just porting Android to a device | 10:54:49 |
| atemu12 | Robotnix merely facilitates the build of the finished port | 10:55:04 |
 @angryant:envs.net | In reply to @atemu12:matrix.org
That's just porting Android to a device Not following. The linked source is of an android kernel + device tree. | 10:56:01 |
| atemu12 | That's just the kernel | 10:56:32 |
| atemu12 | You can (probably) build a binary out of that source and have it boot | 10:56:52 |
| atemu12 | You'd then have, well, Nothing on top of Nothing ;) | 10:57:08 |
| atemu12 | For a functional phone, you need an Android system running atop the kernel | 10:57:30 |
| @angryant:envs.net | So the robotnix feature list item "Custom built kernels" relates to something else? | 10:57:31 |
| atemu12 | Those are for Pixel phones which are built with pre-built kernels by default upstream AFAIK | 10:58:27 |
| atemu12 | What Robotnix does here is build the kernel itself and inject that binary instead | 10:58:50 |
| atemu12 | Again, that's just the kernel | 10:58:59 |
| atemu12 | You still need the rest of Android to have been ported | 10:59:21 |
| @angryant:envs.net | Substituting the linked kernel in that process would not produce something usable? | 10:59:30 |
| atemu12 | Sorry, could you clarify that question? | 10:59:51 |
