Samsung silences benchmark tests on new foldables – a software fix, not cheating

Samsung has pulled the plug on benchmark testing on its latest Galaxy Z Fold 8, Z Fold 8 Ultra, and Z Flip 8, a move that initially sparked accusations of cheating, but now appears to stem from a software quirk rather than deliberate manipulation.

Engineering firmware holds the key

According to sources, the devices are currently running June’s engineering firmware – a pre-release build distinct from the final software slated for consumer release. This technical hurdle prevents installation of popular benchmark apps like AnTuTu, Geekbench, and 3D Mark, effectively silencing their performance analysis capabilities.

A history of controversy

This isn't Samsung’s first rodeo with benchmark scrutiny. Back in 2013, the company vehemently denied accusations of gaming results on the Galaxy Note 3’s CPU and GPU tests. Their defense then centered on the inherent demands of these tests, pushing processors to their maximum frequencies – a justifiable, albeit somewhat opaque, explanation.

The reality: engineering builds

However, a Samsung spokesperson has now confirmed the situation. The units currently in the hands of reviewers – and therefore, unavailable to the public – are indeed running this preliminary software. Once the final build arrives, these restrictions will be lifted, granting access to the performance metrics consumers expect.

Trade-in deals offer a discount

Despite the testing limitations, Samsung is offering enticing incentives. Pre-orders for the Galaxy Z Fold 8 Ultra are discounted by a significant $1200 – a 63% reduction to $899.99. Trade-in offers can boost this further, with eligible devices potentially receiving a $1200 credit. The Galaxy Z Fold 8 also boasts a $1200 discount, or $699.99 with a trade-in, and a $200 Samsung credit if no trade-in is offered.

A solid reason, not a smokescreen

Ultimately, the decision to restrict benchmark access is rooted in a legitimate technical constraint – the engineering builds. It’s a pragmatic response to ensure a consistent and reliable performance profile for the final, retail-ready devices. This isn’t about masking performance; it’s about controlling the testing environment until the software is fully polished.