Apple Lightning (2020)
nyansatan.github.io
nyansatan.github.io
Maybe the Pro models will have the full USB C capabilities - video over USB C and full USB 3 speeds like the iPad Pro.
Best hope for USB-3 will be an updated MagSafe connector on a portless phone, using 60ghz networking from phone to MagSafe and usb-C from MagSafe out.
The AirPods Pro2 would have been the perfect opportunity to go wireless. It already works with both standard Qi chargers and the non standard Watch charger
It reduces the attack surface (you can't break into the phone by plugging something into it)... which also means that jailbreaking will be a bit more difficult.
It also completely removes them from the debates and regulation of connectors. Lightening? micro usb? usb-c? All of that goes away.
By removing cords and cables it also removes the "my device doesn't work because I was using a flaky 3rd party cable" ongoing support questions.
> The MagSafe Duo Charger conveniently charges your compatible iPhone, Apple Watch, Wireless Charging Case for AirPods, and other Qi-certified devices. Just place your devices on the charger and a steady, efficient charge begins on contact. The charger folds together neatly so you can easily take it with you wherever you go.
They'd need to move the entirety of the wireless power transfer devices and accessories to some other standard.
In the scenario you describe, the EU wants Apple to remove a nonstandard lightning connector and replace it with a standard one for increased interoperability and decreased e-waste.
It looks like what you describe is exactly what happened, which is exactly what the EU wanted.
Why do you think it's a bad thing?
Do you think governments mandating that analog telephones used RJ-11 and twisted pair to be bad?
What about mandates on electrical receptical standards?
When the iPad Pro was a host - ie you connect a usb 3 storage device to it via the camera connection kit - basically a lightning to USB adapter, you could get USB3 speeds.
But if you tried to connect it to your computer, it would be USB 2.
And I believe this is because all Lightning to USB cables (be it USB-A or USB-C) only support USB 2.0.
The Camera Connection Kit supports/supported USB 3.0.
In my experience it works well for 2-3 years then wears out and charging becomes very difficult after that. The connector also breaks easily as it is essentially a totally exposed fragment of a circuit board.
The design was light years ahead of everything else for a long time but these days, everything should be USB-C.
But USB-C is pretty young. It remains to be seen if cables and connectors are really durable forever.
I am still suspicious of the complexity of the nested male/female design with the inner male blade being part of the device and hard/impossible to fix if broken. . . but have not seen any problems on my increasing number of USB-C devices yet.
It was totally designed to enable a minimalist Apple retail store aesthetic. I'm convinced that's the only reason for the design. Totally unnecessary design constraint, but very cool...talk about a company with a holistic view of their products, thinking about how details of the design will aid retail display.
I'm still looking forward to a USB-C iPhone, if Apple doesn't go portless (fingers crossed on that).
At the samy time, my USB-C cables just work.
If the references to authentication and certificates weren't enough, there is definitely some DRM crypto going on in there. Yet the Chinese were able to clone the 1-wire authentication chip within a week or so of the official products' release.
Some jurisdictions take stealing energy as a crime. Germany, for example, has up to five years of prison on the books [1].
Kids, don't mess around with energy if you don't exactly know what the f..k you are doing and know the legal and technical risks involved.
In general stealing anything is frowned upon and is at best a temporary imbalance in technical ability to steal versus economic incentives to stop theft.
Besides, courts have ruled that even charging a phone at your workplace without authorization fulfilled the criteria, the case was only thrown out later on because firing someone over stealing 1.6 cents worth of electricity after 19 years of employment is ridiculous [1].
2. The idea is you'd be tricking the supercharger into letting you pay for it, not necessarily stealing it.
Where? Will you post some links?
https://www.eevblog.com/forum/oshw/oshw-apple-lightning-conn...
It's likely they reverse-engineered and managed to extract a key from a real one.
I think the desire to only use a single wire for signalling is understandable, at least in setups where there are physical wires, rather than tracks on a flex PCB, running from LED to LED.
Since every rising edge is the start of a new bit, encoding each bit with an H followed by an L makes the signal self-clocking. With this, the two sides don't need very accurate -- or shared -- clocks.
With the tolerances specified in the datasheet, to tell a zero from one the receiver only needs to tell whether a pulse is shorter (T0H) or longer (T1H) that 0.5us.
T0L and T1L are indistinguishable (their allowed durations overlap) and don't need to be measured by the receiver. That said, I do agree that it's weird that they weren't chosen such that T0H+T0L=T1H+T1L at the centre of the tolerance range.
It's likely they intended them to be the same, but for whatever reason the design characterisation discovered the distribution of periods are actually slightly different from the ideal design, so instead of trying to do a potentially very expensive redesign, they just documented the reality and left it at that.
> To send a binary number "1", the bus master sends a very brief (1–15 μs) low pulse. To send a binary number "0", the master sends a 60 μs low pulse. The falling (negative) edge of the pulse is used to start a monostable multivibrator in the slave device. The multivibrator in the slave reads the data line about 30 μs after the falling edge. The slave's internal timer is an inexpensive analog timer. It has analog tolerances that affect its timing accuracy. Therefore, the pulses are calculated to be within margins. Therefore, the "0" pulses have to be 60 μs long, and the "1" pulses can't be longer than 15 μs.
The other “simple” protocols you mention all require a clock line, whereas 1-Wire/IDBUS do not. UART comes closer, except it requires both devices maintain their own independent, reasonably accurate clocks. (How do you tell whether that long high pulse was 4 or 5 1-bits in a row if your clock is terrible?) If you’re trying to design a very simple system that needs to work with wildly inaccurate clocks, you need some kind of self-clocking protocol, like this, where the difference between a 1 and a 0 bit is an order-of-magnitude difference in pulse width.
When I was a teen, me and a friend built a device (for a competition) that could encode and decode messages onto a roll of receipt paper by moving the paper across a reader/writer head (a sharpie attached to a servo, and a photosensor) to draw and read lines. Clocking turned out to be by far the hardest problem, because the speed at which the paper moved was too unpredictable and inconsistent (it depended on battery level, inconsistencies in the motor, how heavy the roll was, how hard the marker was making contact with the paper, etc), We spent many hours designing, testing, and tweaking the software and hardware until we arrived at basically this exact encoding scheme — plus a Hamming code based on letter frequency since we were encoding English messages. We felt very proud of this elaborate way to encode text — until we realized we had just reinvented Morse code.
https://wp.josh.com/2014/05/13/ws2812-neopixels-are-not-so-f...
Apple Lightning - https://news.ycombinator.com/item?id=23705546 - July 2020 (229 comments)
The EU is forcing them to do so by mid-2024, so it is widely believed that the iPhone 15 will be USB-C.
The Siri Remote and AirPods charging cases already are.
Personally, I think apple has wanted to switch to USB-C for a while on iPhone. They waited until the EU actually passed legislation so they could find a person to point fingers at when their customers complained about accessories breaking compatibility.
I’ve got an iPad mini and what I really want is a USB oscilloscope that works with it
It's always been there, lightning is just a connector, the physical protocol is USB.
> Personally, I think apple has wanted to switch to USB-C for a while on iPhone.
Yes, but also after the DC -> Lightning transition they kinda promised there would be no new transition for a while, which was pretty safe at the time, but USB-C landed a few years later.
I actually expected the iPhone 14 to switch, as 2022 is the 10 years anniversary of Lightning, and about how long the Dock Connector lasted (although technically it survived until this year and the discontinuation of the iPod Touch).
The iPod Touch has been using Lightning since the 5th generation released in 2012.
The decade is up.
Personally I would be happy to keep lightning. It’s simple, it works. I have many lightning cables. If I see I lightning cable I know exactly what it’s for. With USB-C you can’t know the capability of the cable by looking at it.
But I suppose lightning has had it’s term in office and it’s time to move on.
The goal was to reduce waste and they already included in the same regulation that if companies don't agree on a common tech for wireless (like it is now) but go their own way to sell exclusive ones that can't be used with other brands then they would regulate that too.
Do you also include that actual charger and not only the cable part? Can you show me your numbers, do you mean by weight/volume , CO2 wasted in creating and shipping the chargers ?
But there are more benefits by using a standard port, I can use a Samsung charger for a table in my Asus phone, I can share a charger for 2 products and not buy a new one if the old one is gone.
But, IMO, from a cable and connector standpoint, USB-C is worse than Lighting.
You can completely ignore the different cable capabilities.
Also, my arguably 20 year old high school-level knowledge tells me that charging by induction will by necessity waste more electric energy than a cable would.
On the iPhone X it was so bad that you couldn't use Facetime while on a wireless charger, because the phone would throttle the CPU after 10 minutes or so because the phone got too hot.
Not sure if they fixed it on later models, but I guess this is why they are limiting charging power. Glass and stainless steel aren't particularly good heat conductors.
Maybe Magsafe support more power because the exact alignment reduces waste heat.
MagSafe however can charge up to 15 watts.
So in some respects it is still a proprietary connector.
I doubt they will let anything compete with MagSafe short of more EU regulation.
[1] https://www.sammobile.com/news/new-galaxy-watch-4-update-sol...
Just place a phone/charging case on a Qi charger? Doesn't CarPlay support wireless communication? Android Auto does.
They are not. Even latest models from September still use Lightning and wireless only.
Until then I’m sticking with my 8 euro Xiaomi Bluetooth earbuds.
that's patently not true, bought latest airpods pro last week to my wife and it still has that obsolete lightning port
It is in the works, though: https://www.theverge.com/2022/8/9/23298151/apple-usb-c-airpo...
https://www.usb.org/document-library/usb-type-cr-cable-and-c...
https://www.usb.org/document-library/usb-30-adopters-agreeme... is the agreement- it’s royalty free, basically “sign here, don’t patent our stuff”. Not “open source”, but it’s pretty reasonable for what you get IMO- we live in a world all about IP. Many international standards are worse. Plus, it’s not like they’re gonna sue you if you don’t sign it, unless you attempt patent shenanigans.
The $$$$ agreements for VIDs and trademark rights on the other hand… can’t say I’m too fond of those ones.
micro-USB would likely not have improved much without some kind of competition. a big part of why USB-C is reversible was because Apple (and others) made reversible connectors and people showed a lot of preference for that.
USB-Cs limitations (that I am already aware of) are: that it consumes a lot of internal space on devices (which we’re feeling less and less as our phones get bigger: but our watches are relegated to wireless charging with no data pins for example), that it's not clear what cable/device can do what (something original USB tried to address with "host" and "client" connector classes) and that it handles comparatively fewer insertion/removal cycles (than lightning, at least).
Regardless: I’m not sure that I am ever happy saying something is “good enough” in perpetuity, even if I cant see all the potential shortcomings of device requirements right now.
You are absolutely right though, the switching cost is high: and monopoly makes it higher.
(FWIW I agree with the EU on this decision, I remember phones before the common charger mandate and that was a nightmare)
USB-C won't be reasonably "good enough" until all I need to reasonably use USB-C devices with USB-C computers is USB-C cables.
Suppose I have a computer with a USB-C port, and half a dozen USB-C peripherals that I want to connect at the same time.
Before USB-C it was simple when I had way more devices than ports. I'd buy an inexpensive USB hub. The hub connected to a computer's type A port using the same kind of cable that my peripherals used to connect to the computer's A port. The hub had several type A ports that could then by used for my peripherals, using that same kind of cable.
If the peripherals needed more total power than my computer's type A port could provide, I could buy an inexpensive powered hub.
Now, with USB-C, the inexpensive USB-C hubs connect to the computer with a C to C cable but usually only have one (or zero) fully functional USB-C ports for peripherals. The rest are type A ports.
To actually get a hub that adds multiple fully functional USB-C ports to a computer it seems the right now you have to buy an expensive Thunderbolt 3 or 4 hub.
The best I've seen for inexpensive USB-C port expansion is this [1] or this [2]. The first provides 4 downstream USB-C ports, but they are data only, with no power or video support. The second is the same as the first except it also provides a fifth USB-C port that appears to be a power input only you can use with a USB charger to provide power to allow the hub to power or charge your computer.
[1] https://www.amazon.com/Minisopuru-Ports-USB-Hub-Chromebook/d...
[2] https://www.amazon.com/Minisopuru-Ports-USB-Hub-Chromebook/d...
- Reversible: Useless gimmick that nobody asked for
- DisplayPort alt mode: Useful in theory, but no phones support it in practice
- Symmetric: Host-side USB-C never ended up being mainstream anyway (and AB ports already existed anyway)
- USB3: micro-B already had the "3.0 appendage", if anything turning it internal made it easier for manufacturers to silently revert to USB2
- Power Delivery: Qualcomm QuickCharge already existed and could have been standardized without a new connector
- DisplayPort alt mode: Every laptop uses this. It's what lets us have docks with display outputs.
- Symmetric: Every laptop has host-side USB-C.
- USB3: The micro-B "3.0 appendage" is ridiculous and huge, and no device which uses micro-B ended up supporting it in practice (except for I believe a couple Samsung phones?)
- Power delivery: Qualcomm QuickCharge is proprietary garbage. It could have been standardized yes, but is there any reason to believe Qualcomm would have wanted that?
- And it turns out it's incredibly useful to have both Power Delivery and DisplayPort and data transfer in one cable. It allows the world we currently live in where you can have one dock connected via one cable which handles video, power, USB, networking, audio, etc. (And yes, docks are generally too finicky, there's a lot to complain about in terms of implementation. But the idea is solid.)
Nearly every external portable HDD I've seen has these (and comes with a corresponding short USB 3.0 micro-B to A cable).
Apple using it as an excuse has nothing to do with it being a problem in the real world.
> it breaks way too easily and seems to take very few connection cycles before it stops making a good connection.
Never even heard of this actually happening in practice at the time. How hard were you pushing them in?!
> - Symmetric: Every laptop has host-side USB-C.
A few laptops have it. No peripherals (outside of those docks) actually use it because the hubs barely exist and very few have more than one.
> The micro-B "3.0 appendage" is ridiculous and huge
So? It's still tiny compared to the cable itself, this isn't a real problem.
> and no device which uses micro-B ended up supporting it in practice (except for I believe a couple Samsung phones?)
Those devices don't supposed 3 over USB-C either. If anything, USB 3 support in peripherals has declined the last few years.
> - Power delivery: Qualcomm QuickCharge is proprietary garbage. It could have been standardized yes, but is there any reason to believe Qualcomm would have wanted that?
QCQC over USB-C was a thing too, for a while. I guess we'll just have to wait for USB-D for fast charging!
Huh? USB-C cables already support mandatory 60 watts, optional 240 watts.
Still it doesn't prevent devices from having multiple ports. Newer tech will be picked up first by bigger devices like laptops that will be able to do USB-C and a new port at the same time. Or maybe a phone with two charging ports, the same way the ASUS ROG phone does.
Of course it should be visually different. Like cable with two contacts on each side so you would understand that this cable is not going to provide full speed, but still will work and charge.
It seems inevitable that phones and most tables will move to all wireless eventually. The only thing holding it back is faster charging. The EU standard doesn't prevent Apple from moving to a wireless charging method as I've understood. The regulation only covers the case where you have cable for charging.
So yes, since the new standard will likely be wireless, or semi-wireless (like MagSafe), Apple can probably move to it.
My pet theory for why Apple hasn't moved to USB-C already is they didn't want to send the signal that USB-C is getting long term support on phones from them. Sticking to Lightning forces makers of peripherals to use Bluetooth or WiFi if they want a solution that works for all phones and is future-proof, and I think that's exactly what Apple wants. The problem is the transition has been delayed much longer than they hoped for, since wireless charging technology hasn't developed as fast as they hoped (see the last-minute cancellation of the AirPower charging mat for a dramatic example of their miscalculation there)
In general, the USB-C receptacle seems better designed for longevity.
I swear every other comment on C vs Lightning has a completely different view on which is more robust than the previous
... which is pretty easy to achieve when trying to clean out a socket from pocket lint. It's better than micro and mini USB, yes, but a Lightning-style inversion would have been way more durable.
In any connector of this sort, there are two pieces: the plug on the cable and the receptacle on the phone. Lightning has a very visually appealing and physically durable plug, and that’s the part that you see. But this hides several aspects of the connector that make a poor functionality tradeoff.
On a USB micro B or USB-C cable, the plug is retained in the socket by little spring-loaded clips on the plug. On micro, they’re on the outside and very obvious, and they stop working well if the plug gets a bit bent. On USB-C, they’re in the concealed portion of the plug. In both cases, they are components that can wear out, and, when they do, you replace the cable and you’re in good shape. These spring-loaded clips mate with fixed notches in the receptacle, and those notches are much longer lasting.
Lightning does this the other way around. The plug has notches, and the springs are concealed in the socket. If the springs wear out, replacing the cable doesn’t help.
Similarly, the electrical contacts are springy in the socket. They are very easy to damage with careless cleaning.
Lightning has an additional defect involving arcing. If you look at a charging cable that’s been use for a while, you’ll see that one electrical pad on each side of the plug will be burnt. Presumably this is where the connection arcs every time it’s unplugged. I’m not sure how USB mitigates this, but it seems to be less of a problem. Maybe the contacts are simply thicker and more durable.
Sure, USB-C receptacles gave a tongue, and it’s a weak point, but it’s much stronger than the 10 fragile moving parts inside a lightning receptacle.
My guess is that it's probably just the good old "different length pins" trick. A quick web search shows me that the VBUS and GND pads (which carry the power) on the socket are longer, so the rest of the contacts unplug first. And unplugging the CC contact means that the pull-down resistor on it disappears, which tells the source to stop sending power to the VBUS contacts before they start to unplug.
For data transfer speeds (assuming you picked the right cable), yes. For everything else, no. IMO, Lighting is the better physical connector. The device side connector tends to be what fails with USB-C, Lighting tends to have the cable fail which is what you want in a failure. USB-C cable capability is a mess, though at least we're past USB-C cables frying devices.
As far as ubiquity is concerned, depending on location, Lighting can sometimes be easier to find than USB-C. They are least equal in the US.