Frequently asked questions

Which phones are supported?

Currently, DiamaneOS supports the Fairphone 6 only. The supported-device list is the reference for device support. Check it before installing; similar model names do not imply compatible firmware or partitions.

Why am I seeing a message about my bootloader not being locked during setup?

After installing an official signed DiamaneOS release, this warning means the bootloader-locking step was not completed. Finish that installation step before continuing setup: a locked bootloader enforces verified boot against the expected operating-system key.

Open the bootloader-locking section of the installation guide on your computer. Proceed only when the official release provides locking instructions for your exact device. If those instructions are absent, stop rather than improvise.

In the setup wizard, choose Reboot to bootloader, connect the phone by USB, and complete those locking instructions. Then resume setup.

Locking erases user data. Source-built images signed with Android’s public test keys must remain unlocked. Do not apply another device’s locking instructions to your phone.

Does a user build mean it is a signed release?

No. The user variant disables root debugging; private release signing is separate. A build flag or filename cannot establish authenticity. Check the expected public signing identity and verification records. The build guide explains the distinction.

Can my source build receive project updates?

No. Your source build is not signed with DiamaneOS’s private release keys, so it cannot install project-signed updates. Build and sign your own compatible updates, or follow the installation guide to switch to an official release.

What can the servers see?

The host handling a request can see connection metadata, including your IP address and requested file or service. A VPN substitutes its exit address. DiamaneOS disables request logs; providers have their own visibility and policies. See the privacy policy.

Does attestation prove the phone has no malware?

No. It checks supported hardware-backed identity and boot-state properties against a trusted baseline. It does not prove the absence of every malicious app or vulnerability. A valid result also depends on the verifier and expected OS identity. See attestation explained.

Why publish advertising opt-out files if the site has no ads?

Someone could falsely claim to sell advertising for our domain or apps. Our ads.txt and app-ads.txt declare that no seller is authorised. Advertising systems that check these files can reject that falsely labelled inventory.

These files do not block ads in your browser. GrapheneOS’s sitewide advertising industry opt-out article explains the purpose and limits of the standard.

Where should problems be reported?

Send sensitive security reports to security@diamaneos.de. Use the issue tracker for ordinary bugs, and hello@diamaneos.de or the contact form for general questions. Keep account tokens, private keys and identifying diagnostic data out of public reports.