The “Leaks” Keep Coming: New Images Reportedly Show New iPhone’s Tiny Dock Connector

Chris Velazco is a mobile enthusiast and writer who studied English and Marketing at Rutgers University. Once upon a time, he was the news intern for MobileCrunch, and in between posts, he worked in wireless sales at Best Buy. After graduating, he returned to the new TechCrunch to as a full-time mobile writer. He counts advertising, running, musical theater,... ? Learn More

newdockconnector

If rumors hold true, Apple should be gearing up to unveil its latest iGadgets in just a few weeks, and it’s no surprise that all sorts of questionable leaks are now worming their way into daylight.

The latest of those purported leaks comes in the form of images obtained by the French site Nowherelse.fr that reportedly depict Apple’s tiny new dock connector next to a USB plug. Got your grains of salt ready?

Good, let’s go.

Right now there are so many numbers floating around that it’s hard to make sense of what’s actually happening. TechCrunch and Reuters independently confirmed that Apple’s new dock connector would have 19 pins, but persistent rumors (along with some snippets of code within iOS 6) point to the existence of a 9-pin connector. Still others have been reporting an 8-pin connection, much like the one seen in these pictures.

So what gives? Who’s right?

At this point, who knows. It’s possible that we’re only seeing one side of the connector, and that a handful of pins live on the other side — whomever took the pictures doesn’t seem to have photographed the opposite end of the connector. Well, that or both sides of the plug are identical. It’s also possible that, as MacRumors’ Arnold Kim puts it on Twitter, the metal edge of the connector could effectively serve as a grounding pin, which pushes the number to nine.

Or, if we start paring down possibilities with Occam’s razor, we could also draw the conclusion that the images are fake and that there are better ways to spend a Friday than wracking our brains over Apple minutiae. Either way, there’s no way to get a full sense of what’s going on here.

For what it’s worth, the design doesn’t actually look too bad — I could conceivably see Apple running with something like this, though I have to wonder how sturdy the inevitably big-to-small dock connector adapter is going to be. In any case, there’s no way in hell that these images aren’t going to be followed up by even more leaks and speculation, so hold on for the ride.

UPDATE: Nowherelse.fr has updated their original post with a bit more information about the mysterious connector. iDownloadBlog‘s Sebastien Page (who in addition to being a nice guy speaks fluent French) offers up the following translation:

“We have obtained new information about this connector. We have indeed learned that it is not equipped with 8 but 16 pins with distinct functions (8 pins on each side), noting that one side would currently have no specific function and might be saved for future use.”


View the original article here


This post was made using the Auto Blogging Software from WebMagnates.org This line will not appear when posts are made after activating the software to full version.
-

Comments

Post a Comment

Popular posts from this blog

scala - 'wrong top statement declaration' when using slick in IntelliJ -

Image
i'm porting project scala 2.9 2.10, therefore have use slick instead of scalaquery. i'm using slick 2.1.0 since supports ms access. according this tutorial , upgrade guide changed robs object class , added val robs : why error message wrong top statement declaration , how rid of it? edit: i'm new scala... according this question seems can't put val outside of methods or classes, right? code above directly in packge. right approach slick then? should move code in class or trait? according this changed val robs = tablequery[robs] to object robs extends tablequery(new robs(_)) {} . no warnings or errors anymore. :)
Read more

c# - DevExpress.Wpf.Grid.InfiniteGridSizeException was unhandled -

Image
when using devexpress, see error: devexpress.wpf.grid.infinitegridsizeexception unhandled message="by default, infinite grid height not allowed since grid rows rendered , hence grid work slowly. fix issue, should place grid container give finite height grid, or should manually specify grid's height or maxheight. note can avoid exception setting gridcontrol.allowinfinitegridsize static property true, in case grid run slowly." the problem dxgrid has infinite height. to fix, set height non-infinite. snoop absolutely invaluable this: if "height" xaml element infinite (i.e. 0 or nan ), can set using one of following: option 1: height="{binding path=actualheight, relativesource={relativesource mode=findancestor, ancestortype=uielement}}" option 2: verticalalignment="stretch" option 3: height="auto" hint: use verticalalignment="stretch" if child of grid <rowdefinition height=...
Read more

PySide and Qt Properties: Connecting signals from Python to QML -

i trying run simple pyside appliccation design made in qml. call function in qml python in separated thread. i have following qml view: import qt 4.7 rectangle { visible: true width: 100; height: 100 color: "lightgrey" text { id: datestr objectname: "datestr" x: 10 y: 10 text: "init text" font.pixelsize: 12 function updatedata(text) { datestr.text = qstr(text) console.log("you said: " + text) } } } here application: some imports.... #!/usr/bin/python import sys import time pyside import qtdeclarative, qtcore pyside.qtgui import qapplication pyside.qtdeclarative import qdeclarativeview the qthread worker.... #worker thread class worker(qtcore.qthread): updateprogress = qtcore.signal(int) def __init__(self, child): qtcore.qthread.__init__(self) self.child = child def run(self): ...
Read more