| 25 Jul 2023 |
 gotlou | Hello, I was looking at robotnix today and wondered if it would be possible to build grapheneos for non pixel phones? | 10:54:09 |
| gotlou | It seems I'd just have to provide the vendor kernel and firmware and robotnix would automate the build? | 10:54:45 |
 atemu12 | gotlou: Robotnix plays no major role in that as it depends on whether GrapheneOS can work with ...whatever device definitions you're thinking of? | 12:56:47 |
| gotlou | thanks | 13:11:47 |
|  @pederbs:pvv.ntnu.no changed their display name from pbsds to pbsds (UTC+1). | 19:04:04 |
 samueldr | another way to think about it is that robotnix pins repo inputs, and knows enough about android-tooling-specifics to run a build; so you'd have to generally solve the same problems than a "standard" port of it would require, whatever that means | 21:47:47 |
| 27 Jul 2023 |
|  ribosomerocker joined the room. | 02:59:15 |
| 30 Jul 2023 |
|  @kyub:matrix.org joined the room. | 18:01:20 |
| 5 Aug 2023 |
| atemu12 set a profile picture. | 08:30:59 |
| 8 Aug 2023 |
|  @stas:mainframe.lv changed their display name from Stas to Стасютенька. | 06:54:48 |
| @stas:mainframe.lv changed their display name from Стасютенька to Stas. | 06:55:19 |
| atemu12 | https://github.com/danielfullmer/robotnix/pull/211 | 13:01:07 |
| 9 Aug 2023 |
|  @gsaurel:laas.fr joined the room. | 09:27:55 |
|  @angryant:envs.net joined the room. | 10:50:34 |
| @angryant:envs.net | Given that the Nothing phone has the source of its kernel and device tree available here: https://github.com/NothingOSS/android_kernel_msm-5.10_nothing_sm8475 - is there a path for using that to do robotnix builds onto a Nothing phone? | 10:53:54 |
| atemu12 | There is but it's a long and painful one | 10:54:27 |
| 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 |
