Robotnix | 264 Members | |
| Build Android (AOSP) using Nix | https://github.com/danielfullmer/robotnix | 84 Servers |
| Sender | Message | Time |
|---|---|---|
| 23 Apr 2026 | ||
| I am however unsure whether the two auto-generated overlays (the stock lineage one and the robotnix one) should be merged, or whether they should be two different APKs with distinct names | 21:46:22 | |
| 27 Apr 2026 | ||
| 13:24:10 | ||
| 15:35:26 | ||
| Hello Everyone :) | 15:37:37 | |
| I just want to say thank you to all the devs/contributors to this project! | 15:56:05 | |
| Hey, anyone gotten this issue before?
| 19:15:53 | |
| are you trying to sign a lineageos build perchance? | 20:50:48 | |
| Yeahh, for Fairphone 4 | 21:06:08 | |
| hm, are you creating an entirely new build, or updating an existing one? | 21:10:51 | |
Because if you're creating a new one, I'd recommend setting stateVersion = "3" | 21:11:19 | |
| (signing is known to be somewhat brittle with the earlier state versions) | 21:11:34 | |
| Updating existing one, from back in february. I've set stateVersion to 1, as it seemed to fit the instructions given, after I had updated flake inputs. What is stateVersion really? | 21:12:35 | |
Ah okay, then you should keep your stateVersion fixed to "1" | 21:13:10 | |
| I'm a bit surprised though that the signing seems to have worked back then, I thought LOS signing was pretty much consistently broken until ~march | 21:13:43 | |
| I also regenerated avb key sizes to 4096. I guess that will cause OTA update to fail though :/ | 21:14:18 | |
| Lol, lucky me I guess | 21:14:43 | |
I made backwards-incompatible changes to how exactly the APKs and APEXes are being signed in robotnix, and I introduced | 21:14:48 | |
if it's really just the avb keys that you regenerated (which you shouldn't do btw - you should set avbKeySize to your old value instead ;) ), the OTA upgrade will only fail if you relocked your bootloader | 21:15:29 | |
(OTA upgrades are signed with releasekey) by default | 21:15:42 | |
| Ahh, okok. Thanks. What would you recommend for me to get further? I just figured I should fetch some updates for my phone ya know | 21:15:46 | |
* (OTA upgrades are signed with releasekey by default) | 21:15:47 | |
| hmm, I am very much confused how your initial build worked in the first place, but as a bandaid (ymmv), I'd recommend manually patching over the error by specifying which key the APK should be signed with:
| 21:17:14 | |
| Ah cool! I'll fiddle around and see if I can get it to sign. Thanks! I can send over the state of my flake.lock + .nix etc of where it worked if you want | 21:19:06 | |
| would be great to get some insights, thanks! :) | 21:19:41 | |
| Download robotnix-working-for-pentane.tar.gz | 21:22:35 | |
| Ohh I see now | 21:24:17 | |
| that was from before I added the signing safeguard patch from GrapheneOS | 21:24:31 | |
| * that was from before I added the signing safeguard patch from GrapheneOS to all distros | 21:24:36 | |
| You're quick at this lol, cool | 21:24:49 | |
| i.e. the APEX file from your error message simply was left with its test keys | 21:25:03 | |