Customer Review

Reviewed in the United States on November 19, 2015
UPDATED REVIEW (February 19, 2016) :
Spigen got in touch with me a little while ago and told me they were fixing their cables. When they finally got the new cables into their systems, they offered me a free replacement cable from their Amazon stock which I purchased on Feb 10, 2016. Let's see how it does!

Let's check spec compliance :
I'm using my trusty Chromebook Pixel 2015 with the Chromium Twinkie USB-PD Sniffer, available on Amazon from Plugable : 
Plugable USB 3.1 Type-C (USB-C) Power Delivery Sniffer

For my first test, I've got the Spigen USB 3.0 Type-A to Type-C cable plugged into an Apple proprietary Type-A charger, a 12W iPad charger.

The Type-C end is plugged into Twinkie, acting as a pass through to Chromebook Pixel 2015. Picture attached!

First let's run the ectool command from Pixel's command line to check what Pixel thinks is happening on its USB-C ports :

localhost ~ # ectool --dev 1 usbpdpower
Port 0: SNK Charger Proprietary 4656mV / 2400mA, max 5000mV / 2400mA / 12000mW
Port 1: SRC

So far so good. Pixel identifies the charger as a Proprietary type adapter, and has negotiated 2.4A 12W of charging.

Let's see what Twinkie (the USB PD sniffer) says :
> tw cc
CC1 = 20 mV ; CC2 = 428 mV

The tw cc command reads the instantaneous voltage values from the CC pins. As you can see here, CC2 pin has a value of 428mV. Referring to the USB Type-C Specification Table 4-25 Voltage on Sink CC pins, this voltage falls right in the middle of the range allowed for vRd-USB, meaning that yes, this USB cable has the correct 56kΩ pullup resistor!

One more command :
> tw vbus
VBUS = 4726 mV ; -2452 mA

The tw vbus command uses twinkie's current and voltage meter ability. As you can see, the laptop is pulling just around 2.4A of current at 4.726V from the Apple adapter.

For a USB 2.0 High Speed data test, I’ve hooked my Nexus 5X to my Chromebook Pixel via the Spigen Type-A to Type-C cable to test large file transfer via MTP. It just works, no problem!

For a USB 3.1 SuperSpeed data test, I've hooked up my Pixel C to a Windows 10 laptop using the Spigen cable, and verified that it indeed enumerates at SuperSpeed using the USBView.exe app, and that large file transfers are stable. This is a great cable to have for MacBook users especially who want to use Target Disk Mode, which requires a SuperSpeed capable USB cable.

Now for more subjective judgments of this cable : The Type-C plug on this cable is a stamped metal part that's been wrapped around to the shape of the plug. It does have a seam on one side. What impressed me about this cable is although it is a USB 3.1 SuperSpeed cable, meaning it has four extra wires to support SuperSpeed mode, it is not substantially thicker than many of the USB 2.0 only cables I've seen. It's quite thin and flexible still.

In conclusion : A high quality charging and data sync A-to-C cable from Spigen! The cable is a great safe way to charge and sync newer USB Type-C devices such as Nexus 6P/5X or Pixel devices with your old Type-A equipment. It is future proof for fast charging USB Type-C devices to come, as well as future proof for USB 3.1 SuperSpeed devices!

ORIGINAL REVIEW (November 19, 2015):
Benson again continuing my reviews of USB Type-C legacy cables. This time, I'm reviewing Spigen's A-C USB 3.1 cable.

This cable does not correctly follow the USB Type C specification Release 1.1. To find the specification, please go to usb.org, and look under developers/usbtypec.

Specifically, using this charging cable, the Chromebook Pixel will attempt to draw 3A of current over the cable, potentially damaging the USB hub or charger on the A side, which is not guaranteed to be rated at 3A.

Please see Section 4.11 and the following note :

1. For Rp when implemented in the USB Type-C plug on a USB Type-C to USB 3.1 Standard-A Cable
Assembly, a USB Type-C to USB 2.0 Standard-A Cable Assembly, a USB Type-C to USB 2.0 Micro-B
Receptacle Adapter Assembly or a USB Type-C captive cable connected to a USB host, a value of 56 k
± 5% shall be used, in order to provide tolerance to IR drop on V BUS and GND in the cable assembly.

In other words, since you are creating a USB Type-C plug to a USB 3.1 Type-A Plug assembly, you must use a resistor of value 56k as a pull-up on CC (configuration channel). According to my testing, your cable uses a 10k pull-up, which is not legal when the other end of the cable or adapter is a legacy Type-A or Type-B connector or receptacle.

Please let me know if there is any more information I can provide about why these adapters are problematic.

For consumers, I do not recommend buying this cable, as it may cause damage to your charger, hub, or PC USB ports.
Customer image
5.0 out of 5 stars UPDATED : Spigen's USB 3.1 A-to-C cable has been updated to have compliant CC termination! Great SuperSpeed cable!
By Benson Leung on November 19, 2015
UPDATED REVIEW (February 19, 2016) :
Spigen got in touch with me a little while ago and told me they were fixing their cables. When they finally got the new cables into their systems, they offered me a free replacement cable from their Amazon stock which I purchased on Feb 10, 2016. Let's see how it does!

Let's check spec compliance :
I'm using my trusty Chromebook Pixel 2015 with the Chromium Twinkie USB-PD Sniffer, available on Amazon from Plugable : [[ASIN:B015X29HLM Plugable USB 3.1 Type-C (USB-C) Power Delivery Sniffer]]

For my first test, I've got the Spigen USB 3.0 Type-A to Type-C cable plugged into an Apple proprietary Type-A charger, a 12W iPad charger.

The Type-C end is plugged into Twinkie, acting as a pass through to Chromebook Pixel 2015. Picture attached!

First let's run the ectool command from Pixel's command line to check what Pixel thinks is happening on its USB-C ports :

localhost ~ # ectool --dev 1 usbpdpower
Port 0: SNK Charger Proprietary 4656mV / 2400mA, max 5000mV / 2400mA / 12000mW
Port 1: SRC

So far so good. Pixel identifies the charger as a Proprietary type adapter, and has negotiated 2.4A 12W of charging.

Let's see what Twinkie (the USB PD sniffer) says :
> tw cc
CC1 = 20 mV ; CC2 = 428 mV

The tw cc command reads the instantaneous voltage values from the CC pins. As you can see here, CC2 pin has a value of 428mV. Referring to the USB Type-C Specification Table 4-25 Voltage on Sink CC pins, this voltage falls right in the middle of the range allowed for vRd-USB, meaning that yes, this USB cable has the correct 56kΩ pullup resistor!

One more command :
> tw vbus
VBUS = 4726 mV ; -2452 mA

The tw vbus command uses twinkie's current and voltage meter ability. As you can see, the laptop is pulling just around 2.4A of current at 4.726V from the Apple adapter.

For a USB 2.0 High Speed data test, I’ve hooked my Nexus 5X to my Chromebook Pixel via the Spigen Type-A to Type-C cable to test large file transfer via MTP. It just works, no problem!

For a USB 3.1 SuperSpeed data test, I've hooked up my Pixel C to a Windows 10 laptop using the Spigen cable, and verified that it indeed enumerates at SuperSpeed using the USBView.exe app, and that large file transfers are stable. This is a great cable to have for MacBook users especially who want to use Target Disk Mode, which requires a SuperSpeed capable USB cable.

Now for more subjective judgments of this cable : The Type-C plug on this cable is a stamped metal part that's been wrapped around to the shape of the plug. It does have a seam on one side. What impressed me about this cable is although it is a USB 3.1 SuperSpeed cable, meaning it has four extra wires to support SuperSpeed mode, it is not substantially thicker than many of the USB 2.0 only cables I've seen. It's quite thin and flexible still.

In conclusion : A high quality charging and data sync A-to-C cable from Spigen! The cable is a great safe way to charge and sync newer USB Type-C devices such as Nexus 6P/5X or Pixel devices with your old Type-A equipment. It is future proof for fast charging USB Type-C devices to come, as well as future proof for USB 3.1 SuperSpeed devices!

ORIGINAL REVIEW (November 19, 2015):
Benson again continuing my reviews of USB Type-C legacy cables. This time, I'm reviewing Spigen's A-C USB 3.1 cable.

This cable does not correctly follow the USB Type C specification Release 1.1. To find the specification, please go to usb.org, and look under developers/usbtypec.

Specifically, using this charging cable, the Chromebook Pixel will attempt to draw 3A of current over the cable, potentially damaging the USB hub or charger on the A side, which is not guaranteed to be rated at 3A.

Please see Section 4.11 and the following note :

1. For Rp when implemented in the USB Type-C plug on a USB Type-C to USB 3.1 Standard-A Cable
Assembly, a USB Type-C to USB 2.0 Standard-A Cable Assembly, a USB Type-C to USB 2.0 Micro-B
Receptacle Adapter Assembly or a USB Type-C captive cable connected to a USB host, a value of 56 k
± 5% shall be used, in order to provide tolerance to IR drop on V BUS and GND in the cable assembly.

In other words, since you are creating a USB Type-C plug to a USB 3.1 Type-A Plug assembly, you must use a resistor of value 56k as a pull-up on CC (configuration channel). According to my testing, your cable uses a 10k pull-up, which is not legal when the other end of the cable or adapter is a legacy Type-A or Type-B connector or receptacle.

Please let me know if there is any more information I can provide about why these adapters are problematic.

For consumers, I do not recommend buying this cable, as it may cause damage to your charger, hub, or PC USB ports.
Images in this review
Customer image
Customer image
150 people found this helpful
Report abuse Permalink