| 7 May 2025 |
 Manu [tennox] | I've never built a ROM but love NixOS on my laptop, and thought it would be awesome for my android (oneplus 6T) as well...
Lineage 22.2 is officially supported.
Am I totally naive to try to get robotnix to build it? | 11:34:48 |
| Manu [tennox] | currently failing at this step - added to supported_devices.toml, but get this:
❯ ./update_device_dirs.py --branch lineage-22 oneplus_fajita
SKIP: lineage-22 branch does not exist for fajita
trying git ls-remote https://github.com/TheMuppets/proprietary_vendor_oneplus
SKIP: lineage-22 branch does not exist for https://github.com/TheMuppets/proprietary_vendor_oneplus
| 11:35:50 |
| Manu [tennox] | * currently failing at this step - added to supported_devices.toml, but get this:
❯ ./update_device_dirs.py --branch lineage-22 oneplus_fajita
SKIP: lineage-22 branch does not exist for fajita
trying git ls-remote https://github.com/TheMuppets/proprietary_vendor_oneplus
SKIP: lineage-22 branch does not exist for https://github.com/TheMuppets/proprietary_vendor_oneplus
That repo seems un-updated since 3 years... 😥
| 11:38:41 |
| Manu [tennox] | apparently TheMuppets just started using separate repos for the devices:
https://github.com/TheMuppets/proprietary_vendor_oneplus_fajita
| 11:50:06 |
| Manu [tennox] | So after some hacks in the updater script the build is running, not sure if I did something wrong
https://github.com/nix-community/robotnix/compare/master...tennox:robotnix:fajita-22 | 12:05:24 |
| 8 May 2025 |
 atemu12 | The old bad update script has a whitelist branches where it tries the device-specific one | 12:36:58 |
| atemu12 | There's a condition somewhere that checks the branch and does it this way | 12:37:36 |
| atemu12 | You could flip that so that it's a whitelist for old branches | 12:38:14 |
| atemu12 | Or remove it entirely because I don't think anyone cares for updating a branch that's old enough to have the combined vendor dir | 12:38:31 |
| atemu12 | I have done some preparations for 22.2 using the old script but haven't gotten around to finishing it | 12:39:19 |
| atemu12 | You should do 22.1 for now; that ought to work | 12:39:35 |
| Manu [tennox] | I got so close, but build fails in the end:
https://github.com/nix-community/robotnix/issues/292 | 15:00:04 |
| Manu [tennox] | * thanks 🙏
I got so close, but build fails in the end:
https://github.com/nix-community/robotnix/issues/292 | 15:00:24 |
| atemu12 | Is that with your changes from above or with what I recommended you to do? | 15:14:07 |
| atemu12 | btw. that's just the build of the build process, the actual build didn't even start yet ^^' | 15:14:22 |
| atemu12 | The error sounds to me like it's missing some directory that should be there | 15:15:01 |
| atemu12 | I don't recognise which one it is | 15:15:09 |
| 14 May 2025 |
|  eldritchcookie joined the room. | 20:32:07 |
| 19 May 2025 |
|  oak 🏳️🌈♥️ changed their display name from oak 🫱⭕🫲 to oak. | 10:59:12 |
| oak 🏳️🌈♥️ changed their display name from oak to oak 🏳️🌈♥️. | 11:00:58 |
| 21 May 2025 |
 autra | Hi! I've built lineage os for my phone with robotnix, with microg enabled. However, the self-test reports that signature spoofing is not enabled. From microg documentation, it says that lineageos should be supported out-of-the-box. Any idea what could go wrong? | 08:46:52 |
| atemu12 | LOS checks the signature and it must match upstream | 09:30:07 |
| atemu12 | Otherwise you get no signature spoofing | 09:30:25 |
| atemu12 | That's where I'd check first | 09:30:33 |
| autra | Thanks! What signature are you mentioning? | 21:36:32 |
| autra | another possibility, apparently on LOS the signature spoofing is active only for a few selected app, which might explain why the settings app doesn't see it... Although other applications also complains that I don't have google services... | 21:37:36 |
| atemu12 | It's only active for com.google.gms whatever and it must match the upstream μG signature | 21:39:30 |
| atemu12 | Other apps likely won't see it as GMS when signature spoofing isn't working | 21:40:07 |
| atemu12 | I never ran into that error though, so I don't know how it looks like | 21:40:24 |
| atemu12 | Enabling the μG option has always worked for me, so I don't know what you're doing wrong | 21:40:59 |
