Mike

My mistake then. I was primarily concerned with older 22.04 systems I have this deployed on and didn't look enough to find it in 24.04 apparently. Generally I'd recommend installing...

Also, it appears the `--force` can't handle the case where the `/nix/tmp-install-dir` is still present and populated, even though the `--force` option literally says it will overwrite existing files.

It appears the intended way to re-run a failed partial install is to copy `/nix/receipt.json` somewhere else, then call `nix-installer.sh install ./receipt.json`, effectively using a copy of the prior receipt...

This seemingly intentional(?) behavior is guaranteed to always fail. Ignition runs from the initramfs, when systemd-userdb isn't available. Resultantly, it can never detect the users specified via JSON file drop...

> This should probably be an issue against Ignition instead. The issue is that `coreos-assembler` (or possibly something in `rpm-ostree compose` or `osbuild`?) is generating an ignition file it shouldn't....

From reading the IMS Single Registration notes, and the comments above, it sounds like IMS Single Registration can be expected to be phased in by carriers regardless of RCS, the...

@cb474 I'm certainly not an expert on this, I'm just going from what I read in the linked description, what I've read about Android permissions architecture, and some years of...

Just addressing Daniel's point too: This is a new OS feature (IMS_SINGLE_REGISTRATION) being required for a new carrier feature (RCS) that currently is only even available on OEM Android devices...