GrapheneOS explains why Pixel 10 stable builds are delayed, and when to expect camera parity

It has been over a month since GrapheneOS released the first experimental builds for the Pixel 10 series. Arriving back in late November 2025, just days after the team promised support would arrive within “a couple of weeks“, the initial release was a welcome sight for privacy enthusiasts who upgraded to Google’s latest flagship.

However, as we roll into 2026, those builds remain tagged as “experimental.” While early adopters expected a transition to the “Stable” channel sooner, the team has confirmed that significant hurdles remain. In a post on X, GrapheneOS has clarified exactly what is holding up the stable release: it’s not the software features, but rather hardware connectivity.

USB connectivity is the main blocker

While users have been meticulously documenting hiccups in the experimental build, ranging from minor UI glitches to app compatibility, the developers have identified USB connectivity as the primary culprit preventing a stable tag.

Addressing the community, the GrapheneOS team stated:

“The main current issues are with USB connectivity which is the main reason Pixel 10 support is still marked as experimental. It will get better and should be very solid in a few months.”

This perhaps explains the “urgent priorities” the team alluded to last month. In early December, GrapheneOS noted that while RCS support for AT&T and T-Mobile was planned, it was not being actively worked on due to higher-priority tasks. It is now clear that stabilizing the Pixel 10’s core hardware functionality was likely the priority taking precedence.

Camera parity coming in March

Aside from USB issues, the camera experience on the Pixel 10 running the experimental GrapheneOS build has been a mixed bag for early testers. Users have reported specific annoyances, such as the inability to start video recording with the front camera and noticeably degraded quality when using the front lens within third-party apps like WhatsApp.

The team is well aware of these limitations and has provided a concrete timeline for a fix. According to their statement, the GrapheneOS camera implementation “should end up matching the stock OS after the next major update in March.”

This suggests that while the USB issues might be resolved sooner to push the build to stable, full photographic parity with Google’s stock processing is a few months out.

For now, Pixel 10 owners running GrapheneOS should be prepared to stay on the experimental track a little longer. If you rely heavily on USB data transfer, Android Auto, or wired peripherals, you might encounter instability. Similarly, if your workflow relies on pristine front-facing video calls via WhatsApp, you might want to hold onto your secondary device until the March update drops.

While the developers focus on squashing Pixel 10 bugs, they haven’t stopped looking out for user privacy in other areas. Just days ago, GrapheneOS issued a warning regarding the “privacy-first” carrier Phreeli, advising users to opt for alternatives like Silent.Link for eSIM needs instead.

We will keep you updated as the Pixel 10 builds progress toward stability.

We stand out from the tech-media crowd because we break news stories; we mainly bring you stuff that you won’t find anywhere in the mainstream tech media. Our stories have been picked up by some of the world’s most popular websites and media outlets—more info is available here.