Although this week was meant to be all about Samsung with the release of the long-awaited Galaxy S III powerhouse, Apple – as it does – has unwittingly spoiled the party as the tech world becomes engrossed by leaks of the upcoming iPhone device.
The story so far, is that the device will break from the 3.5″ diagonal screen measurement by offering a 1,136-by-640 display, while also receiving an overhauled back plate as part of a unibody design. Although we’ve had a sneak at the new Maps app, little is known about what else could be in store, so the guys over at 9to5Mac have had a little look at the innards of the current iOS 6 beta to see what the state of play may be, yes, a beta of iOS 6.
They found an iPhone running iOS 6 includes Darwin Kernel Version 13.0.0, while the processor is an ARM S5L8950X. In layman’s terms, it ups the ante on both the S5L8940X of the iPhone 4S and the S5L8945X on the new iPad, but doesn’t tell us any juicy info regarding fab size, cores or processor speed.
Currently being referred to under the “A5-***” pseudonym internally (last three characters obscured to protect the leaker), the new processor will more likely than not continue to carry the “A5” moniker as opposed to stepping up to “A6,” although this is more educated guesstimation on the part of 9to5Mac and its sources.
It will feature an entirely new GPU, although nothing else has been ascertained other than the fact it will be new, while the next iPhone will also feature 1GB of RAM. It’s only speculation, but since Apple released quad-core graphics with the latest iPad, the next iPhone could also follow suit. With the screen getting a little longer, and the rivaling companies going big on hardware, it’s certainly something Apple could implement.
The report also states iOS 6 is in the latter stages of development, so without counting unhatched eggs, the Fall deadline for release alongside the new iPhone shouldn’t be too much of a stretch.
With regards to Maps, which we’ve talked about earlier this week, Apple plans on changing many of the UI elements before finalizing, thus the mocked-up screenshot may not be an accurate visual representation of the real thing.