Catcrafts/fp6-img
Watch
2
0
Fork
You've already forked fp6-img
 0
Code Issues Pull requests Projects Releases 3 Packages Wiki Activity Actions
fp6-img/README.md

52 lines
1.9 KiB
Markdown
Raw Normal View History

scaffold: aports overlay, build script, CI workflow, README Kernel aport forked from pmaports 7.1.2-r0, repointed at milos-linux combined-stable with the tested FP6 config (+EFI_ZBOOT for packaging); imsd + nftables aports from the pending pmaports submission. build.sh carries TODO(validate) markers - not yet run end-to-end. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-08 15:42:45 +02:00
# fp6-img
the images follow the upstream rename: postmarketOS is Nura postmarketOS renamed itself Nura on 2026-09-27 (https://nura.eco/blog/2026/09/27/nura-rename/). The README intro, install.sh's messages, the 'latest' release title, the build headers and the default-login lines now say so. Identifiers keep their names - package names, the pmaports and mirror URLs, pmbootstrap - until upstream moves them. The intro also stops calling the images nightly: the schedule trigger is commented out, CI builds on push.
2026-10-12 15:51:36 +02:00
Flashable [Nura](https://nura.eco) images for the
**Fairphone 6/6+**, built from the
scaffold: aports overlay, build script, CI workflow, README Kernel aport forked from pmaports 7.1.2-r0, repointed at milos-linux combined-stable with the tested FP6 config (+EFI_ZBOOT for packaging); imsd + nftables aports from the pending pmaports submission. build.sh carries TODO(validate) markers - not yet run end-to-end. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-08 15:42:45 +02:00
[Catcrafts milos-linux](https://forgejo.catcrafts.net/Catcrafts/milos-linux)
README, install.sh: imsd 1.0.0 finds the P-CSCF itself, the setup section goes imsd 1.0.0 reads the carrier's P-CSCF from the ims PDN at every start, so the section that had every user find it with adb and write /etc/imsd.env goes, as does install.sh's closing hint; the file remains for overriding the address or naming one where the network gives none. The intro no longer presents imsd as a preinstalled extra; it is linked where VoLTE is listed.
2026-10-12 01:17:32 +02:00
`combined-stable` kernel branch.
scaffold: aports overlay, build script, CI workflow, README Kernel aport forked from pmaports 7.1.2-r0, repointed at milos-linux combined-stable with the tested FP6 config (+EFI_ZBOOT for packaging); imsd + nftables aports from the pending pmaports submission. build.sh carries TODO(validate) markers - not yet run end-to-end. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-08 15:42:45 +02:00
Maintained by [Jorijn van der Graaf](https://catcrafts.net/about)
(TheMightyCat) at [Catcrafts](https://catcrafts.net/).
## What works
Everything on the `combined-stable` branch: display, touch, wifi, cellular
data, NFC (reader), speaker audio, microphone, IMU, magnetometer, barometer,
Install fingerprintd from the registry, so the image unlocks with a finger The daemon's own package CI publishes it to the registry the same way imsd's does, so the image takes it from there: the exact apk a user later gets via apk upgrade, sha256-pinned, re-signed for the chroot. Section 3b now fetches both sets, and every fetched file must have a pin -- the check used to be `grep . | sha256sum -c`, which an empty pin list would have sailed through with nothing checked. Three apks: the daemon, its systemd units, and the session agent, which does nothing until a user writes ~/.config/fingerprintd/fingers.conf. The daemon needs the kernel aport's CONFIG_QCOMTEE=m (pkgrel 101) and fp6-vendor-blobs 1-r2's mbn directive to reassemble the trustlet, both built in this run; 0.2.3 says >=1-r2 so a mismatched pair is refused rather than installed. The CI publish step skips fingerprintd-* like imsd-*: registry-sourced, not ours to republish. README: fingerprint in the list, and the two things a user will otherwise report as a dead sensor -- the lock screen listens for 60 seconds after it appears, and a held press is what the matcher was measured on -- plus the untested question of stock Android's own fingerprints after using this. Verified on the dev phone (fp6 repo journal/fingerprint/, 2026-09-05): the registry 0.2.2 package enrols through Plasma's Users page and unlocks the lock screen; 0.2.3 differs by the dependency and a post-upgrade restart. The image build itself, with the fprintd purge inside the chroot, runs first in CI.
2026-09-05 20:31:37 +02:00
ambient light/proximity, fingerprint unlock through
[fingerprintd](https://forgejo.catcrafts.net/Catcrafts/fingerprintd), plus
README, install.sh: imsd 1.0.0 finds the P-CSCF itself, the setup section goes imsd 1.0.0 reads the carrier's P-CSCF from the ims PDN at every start, so the section that had every user find it with adb and write /etc/imsd.env goes, as does install.sh's closing hint; the file remains for overriding the address or naming one where the network gives none. The intro no longer presents imsd as a preinstalled extra; it is linked where VoLTE is listed.
2026-10-12 01:17:32 +02:00
VoLTE calls (both directions) through [imsd](https://forgejo.catcrafts.net/Catcrafts/imsd).
scaffold: aports overlay, build script, CI workflow, README Kernel aport forked from pmaports 7.1.2-r0, repointed at milos-linux combined-stable with the tested FP6 config (+EFI_ZBOOT for packaging); imsd + nftables aports from the pending pmaports submission. build.sh carries TODO(validate) markers - not yet run end-to-end. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-08 15:42:45 +02:00
## Flashing
README: link the latest release Release notes become dated releases of their own on the releases page, notes only, while the images stay in 'latest'; the download line names the 'latest' release by its link.
2026-10-14 01:41:43 +02:00
Download `fp6-img-{DE}.tar.xz` with your preferred DE from the
[`latest` release](https://forgejo.catcrafts.net/Catcrafts/fp6-img/releases/tag/latest)
fp6-img-plasma: both images are named after their shell The Plasma Mobile archive was fp6-img.tar.xz and the Phosh one fp6-img-phosh.tar.xz, so the unmarked one looked like the only one. Both are now fp6-img-<shell>.tar.xz and extract to a directory of that name; install.sh's messages and the README say so, and the README names the dialer each shell calls with. The release upload takes dist/* and needs no change.
2026-10-12 01:17:32 +02:00
(`{DE}` is `plasma` for Plasma Mobile, calls through Plasma Dialer, or `phosh` for
Phosh, calls through GNOME Calls) and unlock the bootloader
compressed artifcats
2026-08-10 10:40:50 +02:00
([Fairphone's official process](https://support.fairphone.com/hc/en-us/articles/10492476238737)).
README: modem-preserving install via fastboot boot (RAM) + dd Proven 2026-08-09: RAM-booting writes nothing (modemst byte-identical after), so a fresh install that dd's boot_a and userdata from the booted Linux never triggers the ABL's boot-flash NV wipe. Classic flash flow documented as the wiping alternative. Details in journal/modem. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-09 01:25:20 +02:00
readme change
2026-08-09 03:33:33 +02:00
**Install**: with the phone in fastboot mode,
compressed artifcats
2026-08-10 10:40:50 +02:00
```sh
fp6-img-plasma: both images are named after their shell The Plasma Mobile archive was fp6-img.tar.xz and the Phosh one fp6-img-phosh.tar.xz, so the unmarked one looked like the only one. Both are now fp6-img-<shell>.tar.xz and extract to a directory of that name; install.sh's messages and the README say so, and the README names the dialer each shell calls with. The release upload takes dist/* and needs no change.
2026-10-12 01:17:32 +02:00
tar xf fp6-img-{DE}.tar.xz
cd fp6-img-{DE}
compressed artifcats
2026-08-10 10:40:50 +02:00
./install.sh
```
readme change
2026-08-13 23:04:02 +02:00
`install.sh` erases dtbo, flashes the rootfs, **RAM-boots** the kernel, writes the boot partition from
compressed single artifact
2026-08-10 16:22:20 +02:00
inside Linux where the bootloader's NV-wipe cannot see it, then reads the modem
NV back and reports the result. The bootloader never writes `boot`.
install.sh: one-command modem-preserving installer erase dtbo + flash userdata + RAM-boot + dd boot_a from Linux + verify modem NV and report honestly. Shipped in dist/ with every release; README points at it. The one believed-safe-but-unisolated step (userdata flash) is self-verified by the script's final check. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-09 01:29:17 +02:00
the images follow the upstream rename: postmarketOS is Nura postmarketOS renamed itself Nura on 2026-09-27 (https://nura.eco/blog/2026/09/27/nura-rename/). The README intro, install.sh's messages, the 'latest' release title, the build headers and the default-login lines now say so. Identifiers keep their names - package names, the pmaports and mirror URLs, pmbootstrap - until upstream moves them. The intro also stops calling the images nightly: the schedule trigger is commented out, CI builds on push.
2026-10-12 15:51:36 +02:00
Default login: `user` / `147147` (same as official Nura images).
Update README.md
2026-09-06 14:00:13 +00:00
**Never re-lock the bootloader** with a custom image installed.
LICENSE, README, FUNDING.yml: GPL-3.0-only for our code, Forgejo's funding file and the shared footer The repository had no license file. Our own code is GPL-3.0-only; the patches and package recipes carried from other projects keep the license their files name. FUNDING.yml is the file Forgejo reads for a repository's Donate button (Forgejo 17.0 and later: .forgejo/, .github/, then the root of the default branch); it points at https://catcrafts.net/shop/donation. The README closes with the footer shared by imsd, fingerprintd and fp6-img: License, Funding, Copyright.
2026-10-16 23:01:47 +02:00
## License
GPL-3.0-only - see [LICENSE](LICENSE). That covers our own code; patches and packaging carried from other projects keep the license named in their files.
## Funding
https://catcrafts.net/shop/donation - see [FUNDING](FUNDING.yml)
## Copyright
Copyright (C) 2026 Catcrafts® [catcrafts.net](https://catcrafts.net/)
Reference in a new issue Copy permalink