MHL 3.0 brings support for 4K and doubles bandwidth

Mobile High Definition Link, a protocol used in mobile devices to deliver content to the large screen without actually using a separate HDMI port, has been made available on tons of devices. The last iteration, MHL 2.1 enabled full HD 1080p support for mirroring, and with the latest update – MHL 3.0, the consortium has upped the ante with support for 4K. With the new range of 4K TVs doing its rounds in the market, it’s the right time for the consortium that is comprised of Nokia, Sony, Samsung and Toshibha to put forward a new iteration of the technology so that the uptake is gradual, and in line with current trends.

The MHL 3.0 specification capabilities include:

• 4K (Ultra HD): Support of 4K formats up to 2160p30
• Simultaneous high-speed data channel
• Improved Remote Control Protocol (RCP) with support for peripherals such as a touch screen, keyboard and mouse
• Power charging up to 10W
• Backward compatible with MHL 1 and MHL 2
• Latest HDCP 2.2 content protection
• Enhanced 7.1 surround sound with Dolby® TrueHD and DTS-HD
• Connector agnostic – uses as few as five pins
• Support for simultaneous multiple displays

As you note above, the 4K support is really the highlight here. But you do also have to note the inclusion of a high speed data channel that supposedly increases the bandwidth by 2X from the older generation. Thanks to the double bandwidth, the MHL can now handle multiple monitors and peripherals using a single connection, which is really awesome for people wanting to convert their smartphones into a personal computer. As with the earlier versions, you get power charging and 7.1 Dolby surround support out of the box, and thankfully, backward compatibility with MHL 1 and 2.

Definitely a step in the right direction for the MHL technology, especially with support for 4K. However, manufacturers have been asked to wait till early September, after which they will be able to download the specifications and implement them in their devices. Lets look forward to the manufacturer implementations then!