Saturday, May 7, 2016

Samsung Galaxy Tab S 10.5 - 2k/QHD Output to 2k/4k Monitor

The question:
Does anyone know how to get the Tab S to output its native 2k display to a 2k+ monitor?

The background:
I use the Tab S to RDP to a an AWS cloud server effectively giving me an extremely powerful Windows laptop and Android tablet combined. I have an RDP app on the tablet that gives me the native 2k resolution of the tablet which I can then divide into quarters using Actual Multiple Monitors. This effectively gives me a 2x2 array of 1280x800 monitors. The only downside is that the text is tiny! As a result, I'm trying to get the Tab S to output its native resolution (2k) to my new 4k monitor. I tried to output this using the MHL 3.0 adapter sold by Samsung, but it only outputs at 1920x1080 through the MHL 3.0 adapter. I suspect that the Tab S has MHL 2.0 installed but not MHL 3.0.

I'm currently looking at using DiamondMM's BVU5500 adapter. Their website says it works with Android devices running Android 5.0 and higher. Their website then directs purchasers to the DisplayLink app in the Google Play store. I noticed that the DisplayLink app says that it only supports resolution up to 1920x1080. I've emailed them to see if that's still the limitation. Amazingly, they are able to convert 4k through a USB v2 using adaptive software. Annoyingly, it seems like it works for Windows/Macs at 4k but only 1080p for tablets.

If I can get this working, I never have to buy another laptop again as my cloud server will provide the processing power while the tablet is just a dumb terminal with great video. Wifi is generally fast enough (especially over my 4G iPhone hotspot) that the lag is not noticeable.

Specs:
Tablet: Samsung Galaxy Tab S 10.5 (SM-T800) running Android 5.02 with root access
Monitor: Samsung U28E590D (28-inch 4k LED monitor 3840x2160, UHD, 1ms)
Tried: Samsung MHL 3.0 to HDMI adaptor EE-HN910
Looking at: DiamondMM's BVU5500 adapter which is based on DisplayLink's DL-5000 chipset


from xda-developers http://ift.tt/1Tvu4vG
via IFTTT

No comments:

Post a Comment