Android

Forget about the Galaxy S25 and S26, the first Galaxy S27 leak is here


samsung galaxy logo closeup

Robert Triggs / Android Authority

TL;DR

  • Samsung has reportedly started work on the Galaxy S27’s Exynos processor.
  • The chip is apparently codenamed Ulysses and will be manufactured on Samsung’s second-generation 2nm process.

The Samsung Galaxy S25 series isn’t even out yet, but we’ve already seen some Galaxy S26 leaks. Now, a Korean publication has revealed the first details about the Exynos 2700 chip that’s set to power the Galaxy S27 line.

SE Daily (spotted via tipster Jukanlosreve on X) reports that Samsung has started development on the Galaxy S27’s Exynos processor. The chip, which is likely the Exynos 2700, is apparently codenamed Ulysses and will be produced on Samsung’s second-generation 2nm process (SF2P).

This second-generation process is said to be under development with a goal to offer mass production in 2026. Samsung is reportedly aiming to increase performance by 12% compared to the previous-generation process, reduce power consumption by 25%, and reduce area size by 8%.

Samsung chip woes mount

The news comes amidst reports that Samsung has been struggling with low yield rates for the Exynos 2500, which is produced on Samsung’s 3nm process. This has led to speculation and leaks that Samsung will ditch the Exynos 2500 in favor of the Galaxy S25 series being exclusively powered by the Snapdragon 8 Elite processor.

However, it doesn’t look like there’s good news for Samsung’s first-generation 2nm ambitions. Last month, Business Korea reported that Samsung Foundry had issues with 2nm yields at its Texas manufacturing plant. It was claimed that Samsung’s 2nm yields were around 10% to 20%. Chip foundries typically seek yields of 60% or more for mass production.

Got a tip? Talk to us! Email our staff at news@androidauthority.com. You can stay anonymous or get credit for the info, it’s your choice.



READ SOURCE

This website uses cookies. By continuing to use this site, you accept our use of cookies.