There's a high chance of devices being sold with GrapheneOS preinstalled in 2027

Motorola Signature hardware and pricing

• Upcoming 2027 Motorola Signature series teased; current 2026 model is very expensive but competitive with Pixel flagships on specs.
• Street prices vary significantly by region; discounts appear when a new Signature model is imminent.
• Some users like the hardware but dislike design choices (e.g., “fabric-like” back).

Phone cost, value, and longevity

• Many argue flagships are overpriced; others justify high-end phones for performance, camera quality, and long support lifetimes.
• Some prefer midrange (Pixel A-series, iPhone SE/E) or cheap Moto G-type devices, but note performance and update support gaps.
• Repair costs and weak warranties for water damage make expensive phones feel risky.

GrapheneOS value proposition and app ecosystem

• GrapheneOS seen as strong on privacy and security while remaining usable, especially on Pixels.
• Discussion on app sources: Play Store seen as most secure for Play apps; F-Droid criticized for security model; Aurora considered workable but brittle; GrapheneOS’s own store and Accrescent mentioned as preferred.
• Users differ on how much to rely on Google services; some run no Google apps, others use sandboxed Play Services with strict permissions.

Banking, attestation, and payments

• Banking app support is mixed: many banks work fine, some explicitly support GrapheneOS, a few block it via Google attestation.
• Several point to a community-maintained compatibility list and note that contacting banks sometimes leads to fixes or policy rollbacks.
• Tap-to-pay is a major gap: Google’s attestation and wallet requirements largely block NFC payments; a few European alternatives (e.g., Curve, PayPal trials) work but are limited and region-specific.
• Some suggest switching banks or using cards/cash/crypto instead of phone payments.

Preinstalled GrapheneOS devices and trust

• Planned GrapheneOS-preinstalled phones will likely be distributed by a third party receiving devices from Motorola, not directly by Motorola or the OS project.
• Some are wary of buying preinstalled devices from any vendor other than the OS team, citing potential “honeypot” or tampering concerns.
• Others note you can factory reset, verify signing keys / boot hashes, or simply reinstall GrapheneOS yourself and use hardware-based attestation tools.

Bootloader unlocking and long-term viability

• Devices are expected to be unlockable; there is concern about any vendor-dependent web unlock process that could be discontinued.
• Some hope Motorola’s process is closer to Google’s simpler Pixel approach, especially since Motorola is collaborating on ports.

Device requirements and cheap-phone hopes

• Multiple comments explain there likely won’t be a ~€200 GrapheneOS device soon: required hardware features (MTE, secure elements, long-term firmware support) are mostly confined to premium tiers.
• Suggestion: buy slightly older Pixels (especially A-series) to hit lower price points, while noting that cost per year of support is better with newer models.
• One commenter asserts GrapheneOS is “experimental” and suspicious due to funding opacity; others rebut that its strict device list is driven by concrete hardware and security requirements.

Alternatives, ideals, and repairability

• Some users still prefer Pixels over Motorolas, or would rather wait for GrapheneOS on future Pixel A models.
• Others bring up Linux phones (PinePhone, Librem, various European projects) and criticize the broader “security theater” ecosystem, desiring fully open devices without DRM, TEEs, or locked bootloaders.
• Interest in hardware privacy features (physical radio kill switches, SD card slots, headphone jacks, removable batteries) is expressed, with regret that modern secure devices rarely offer them.
• A tension emerges between top-tier security (GrapheneOS + modern SoCs) and repairability/“right to repair” devices like Fairphone; users see these as competing priorities for their next phone.