Next-generation iPhone spotted in the wild...again

Here we go again folks - this time, we'll leave out the whole "a guy walks in to a bar (ouch!)" line.  It would appear that the iPhone HD (as it is being called, we actually have no clue what its production name will be) has surfaced yet again.  This time the folks at Taoviet (what would appear to be a Vietnamese blog) have innocently happened upon Apple's next generation heart breaker and have posted pictures and video (via Tinhte) for the world to see - that is until Apple finds a way to put the long distance kibosh on their detective-like efforts.

The device in question is a 16GB unit - whereas the first time we saw this phone, it was XXGB - that appears to be slightly more polished than the prototype that Gizmodo managed to get their hands on a while back.  This device is missing a fews screws that were noticeable in the first leak, suggesting that we are getting closer to a production unit.  Another clue that it's pre-production is the several X's replacing what would otherwise be an FCC ID as well as a model number.

Rumor has it that Gizmodo isn't the only one who was willing to pay to get their hands on this thing, and Engadget seems to think that the folks at Taoviet were willing to shell out $4,000 for this bad boy - apparently they got a 20% discount.  Not long after the next generation iPhone surfaced, the phone was broken down, yet again, and the internals revealed.  According to Chipworks, the alpha-numeric code on the chip, 339S0084, is representative of Apples new A4 microprocessor made by Samsung.  Additionally, the code APL0398, which is apparent on the iPad's A4 chip, is also on the nextgen iPhone, though no one seems to know exactly what that means, yet.

It will be interesting to see if we have another Apple debacle in our hands, and if so what the reaction to it will be.  This is just the very beginning of it, and we'll bring you more detail as it comes our way. Anyone getting more excited about the potential June launch?  Sound off in the comments!

Via Engadget

Disqus Comments