Robotnix | 239 Members | |
| Build Android (AOSP) using Nix | https://github.com/danielfullmer/robotnix | 74 Servers |
| Sender | Message | Time |
|---|---|---|
| 15 Oct 2025 | ||
logcat full of different errors, but missing aidl is most often and likely relevant | 20:51:26 | |
| Not sure; is there a stacktrace? Android logs tonnes of benign errors that sound critical | 20:51:42 | |
| Like, if the system can't boot for one reason or another, you'll usually have zygote error out with a huge-ass stack trace | 20:52:40 | |
| You could try 22.1 I suppose; that did work | 20:53:17 | |
| Or I guess you could bisect | 20:53:27 | |
| a53d7488adeac921b9b088ef98e52a1761462281 worked | 20:53:54 | |
| 17 Oct 2025 | ||
| 16:41:40 | ||
| good afternoon owo I'm new to matrix, is this the correct room to ask questions about robotnix? | 16:43:26 | |
| Yep | 16:44:50 | |
great, so, about the device option, my device is called guamp and it has 3 variants, is there a way to set the specific variant? | 16:47:05 | |
| https://wiki.lineageos.org/devices/guamp | 16:47:24 | |
In reply to @defalts2:matrix.org
| 16:49:26 | |
| 👀whoops I didn't read that, thank you lol | 16:50:16 | |
| :) | 16:58:36 | |
| 19 Oct 2025 | ||
| Is there a method to specify ./keys as signing keys in nix files? I tried config.signing.keyStorePath = ./keys; config.signing.buildTimeKeyStorePath = ./keys; But I got an error error: A definition for option signing.keyStorePath' is not of type string'. | 11:09:58 | |
That does not make any sense; where is .? | 12:32:44 | |
| Also you don't want to use path literals here as that would copy the key files into the world-readable nix store | 12:33:23 | |
| I've never done signing but you need to pass an absolute path and make it available in the sandbox if you do it this way | 12:34:28 | |
| Pretty sure the docs mention describe how to do that | 12:35:42 | |
| I think you're probably better off using the release script though | 12:35:46 | |
| You should be able to do the full build in the nix sandbox and only sign afterward technically? | 13:22:12 | |
| yes, exactly - that's what the release script is for | 13:27:01 | |
In reply to @atemu12:matrix.orgIt is the folder containing flake.nix and robotnix configurations | 19:29:58 | |
| but that's not in the sandbox is the issue | 20:59:09 | |
| 20 Oct 2025 | ||
| releaseScript says: evaluation warning: releaseScript should be used only if signing.enable = true; Otherwise, the build might be using incorrect keys / certificate metadata. I set signing.enable = true; then I got an error error: The option `signing.keyStorePath' was accessed but has no value defined. Try setting the option. I set it to /keys and added --impure error: path '/keys/f-droid.x509.pem' does not exist | 02:45:46 | |
* releaseScript says: evaluation warning: releaseScript should be used only if signing.enable = true; Otherwise, the build might be using incorrect keys / certificate metadata. I set signing.enable = true; then I got an error error: The option `signing.keyStorePath' was accessed but has no value defined. Try setting the option. I set it to /keys and added --impure error: path '/keys/f-droid.x509.pem' does not exist | 02:45:59 | |
* releaseScript says: evaluation warning: releaseScript should be used only if signing.enable = true; Otherwise, the build might be using incorrect keys / certificate metadata. I set signing.enable = true; then I got an error error: The option \signing.keyStorePath' was accessed but has no value defined. Try setting the option`. I set it to /keys and added --impure error: path '/keys/f-droid.x509.pem' does not exist | 02:46:03 | |
* releaseScript says: evaluation warning: releaseScript should be used only if signing.enable = true; Otherwise, the build might be using incorrect keys / certificate metadata. I set signing.enable = true; then I got an error error: The option \signing.keyStorePath' was accessed but has no value defined. Try setting the option`. I set it to /keys and added --impure error: path '/keys/f-droid.x509.pem' does not exist | 02:46:12 | |
* releaseScript says: evaluation warning: releaseScript should be used only if signing.enable = true; Otherwise, the build might be using incorrect keys / certificate metadata. I set signing.enable = true; then I got an error error: The option signing.keyStorePath' was accessed but has no value defined. Try setting the option\. I set it to /keys and added --impure error: path '/keys/f-droid.x509.pem' does not exist | 02:46:22 | |
* releaseScript says: evaluation warning: releaseScript should be used only if signing.enable = true; Otherwise, the build might be using incorrect keys / certificate metadata. I set signing.enable = true; then I got an error error: The option signing.keyStorePath' was accessed but has no value defined. Try setting the option. I set it to /keys and added --impure error: path '/keys/f-droid.x509.pem' does not exist | 02:46:26 | |