Google Nexus 6P and Nexus 5X were among the first devices to come with support for USB Type-C connectivity, a tech advancement that is now the talk of the smartphone town.
One major plus that this USB Type-C cable comes with is that users can easily plug it into their Nexus 6P or Nexus 5X smartphones without caring which side is up or down. This is basically one of the things that lead to faulty charging ports when it comes to microUSB connectivity. However, this doesn’t mean that the two Nexus devices are free from any faults as far as USB connectivity is concerned.
In the recent past, some negative reviews and comments, in general, have been directed towards USB Type-C cables. Apparently, smartphone manufacturers, as well as some third-party manufacturers, have been accused of bending the laws when it comes to the USB Type-C standards. The result of this is that some cables are in the market yet they supposedly do not meet the required USB-C standards. With the Google Nexus 6P and Nexus 5X also using this type of cables, you might also come across some issues when trying to establish any form of wired connectivity via the USB cable.
If you happen to encounter any USB Type-C cable issues with a Nexus 6P or Nexus 5X, don’t make any attempts of swapping the two phone’s cables. This has been shown in a video by a Reddit user and it shows that using a Nexus 6P USB cable to charge a Nexus 5X (and vice versa) could lead to an overheated or overcharged phone caused by the output of the wrong amount of current. It gets even worse when using the cable with a third-party USB hub. Since the wrong current will be sent to the hub, the on and off button is burnt, thus keeping the hub from being powered down.
The only way to stay free from any of these USB Type-C cables is to stick with the stock cable and charger for your Nexus 6P as well as Nexus 5X. In case of anything, it is better to get a newer cable or charger from the official Google Store rather than get a third-party version, which will bring about the same disaster.
Article View Count: (416)