(skip down to "Questions" if you're in a rush)
Gentlemen,
I have a GNex that I no longer use for phone duty (was replaced with Nexus 4), and am contemplating converting it to a steamer tv box (a la Google TV).
I have a MHL adapter coming today, and I have the portrait-orientation dock as well. Shameful display from Samsung for making mirroring not work past 4.0.3 with the dock, thus a 3rd party MHL adapter is now needed. I have diNovo Mini on controller duty.
I did some testing (GNex on 4.0.2 + Samsung Dock) on a 22" 1080p monitor, and everything just looked huge and bad and blurry with the factory ROM. I installed the latest build of ParanoidAndroid, put the phone in Tablet mode, and shrunk everything as small as it will go. Couldn't test it with the monitor (Dock doesn't mirror with JB) yet, but at least on the device screen, things look more favorable.
Questions --
1 - Is there a recommended ROM for this (other than Paranoid) that will let me Tablet/Phablet layout + scale elements to not look like hell blown up to a 42" 1080p screen ?
2a - Are there any useful media apps I should know about (other than XBMC, Netflix, TV.com, Streamie) ?
2b - Are there any useful utility apps I should know about (other than Sixaxis Controller) ?
3 - Is there a better launcher than stock for this use? (I tried TVLauncher and didn't care for it).
4 - Or, forget about the whole thing and wait for my OUYA to show up in March?
Thanks.
iMediaShare has lots of channels and content for streaming.
Ubuntu comes out soon, you could run XBMC through that and have more control of the UI. I believe Ubuntu goes to a full desktop mode so it'll look good on a monitor/large display.
This would also allow for more powerful remote desktop use too.
I was under the impression that it only mirrors the output, so you need something like http://forum.xda-developers.com/showthread.php?t=1934495 to proceed.
You don't really need full Panadroid, just a DPI change to force tablet mode all the time.
I have a simple question and to be honest, I am a little surprised that googling the issue resulted in nearly no hits. So I am trying my luck now here in the forum:
Part of the reason to buy the Kindle Fire HD 8.9 was for me to be able to use it as a playing device for movies on my HDTV. I also bought the official amazon HDMI to Micro HDMI cable to connect the kindle with my TV. The problem I am now having is that my HDTV (Philips 52PFL9632D) produces two vertical black bars to the left and the right of the picture, i.e. it doesn't offer the full 1920x1080p resolution, but something a little smaller (I guess around 1700x1080p).
Yes, I tried all the scaling options on my TV to no avail. And my Xbox, my BluRay-Player and my Dell Notebook do produce a flawless Full HD 1920x1080p experience on that TV Set on the exact same HDMI port. So it must be a problem of the HDMI output of my Kindle.
I suspect that the reason for that behaviour is the fact that the Kindle 8.9 display features a resolution of 1920x1200, which is not 16:9 but 16:10.
So as a result my TV probably squeezes the picture to fit it and thus produces the black bars left and right. It also doesn't matter if I am playing a video using VLC, surfing the web with Silk or just display the Kindle App selection screen on the kindle. There are always the black bars left and right.
(BTW: amazon customer service acknowledged the problem, but couldn't find an immediate resolution and promised to call be back.)
Does anybody have any idea what I can do to get the full resolution on my HDTV? I was so looking forward to not having to unplug my Notebook everytime and hook it to the TV, but being able to use my Kindle for watching movies instead.
What I am really surprised about:
1. Why does amazon produce a default signal output on the HDMI port larger than 1920x1080 anyways? Most people probably would want to hook it up to their TV and except for some monitors I don't know any TV featuring a resolution of 1920x1200.
2. Why does the kindle not offer any configuration option to at least choose the HDMI output?
3. Why is the net basically not producing any results when I am looking for a solution for that issue? Am I the only one hooking up his Kindle to his HDTV? Or am I the only one having that problem? Or am I the only one being annoyed by seeing two vertical bars on the TV?
ANY help how I can get rid of the vertical bars would be greatly appreciated!
I am going to throw a guess at why its not full 1080, someone can correct me if I am wrong because like I said this is just a guess. From what I heard, the kindle fire HD 8.9" model uses a set amount of ram towards the GPU to render out in the resolution it uses, and from what I read it was just barely enough memory for it to use that resolution, so using anything higher than that would probably not be possible. Lemme see if I can find where I read this.
Edit: found it!
ignoramous said:
The wallpaper service public APIs were selectively disabled to alleviate the memory pressure on system_server. Amazon's default Kindle Launcher doesn't need wallpapers (yeah I hear you when you say apps with FLAG_SHOW_WALLPAPER however do need wallpapers... but that functionality was apparently deemed not *that* important).
We freed about 14MiB+ worth RAM from system_server. This change was primarily targeted at the 8.9 Kindles, as 1GiB RAM was barely holding up to Kindle's massive resolution.
I see that having a bool in framework had work cut out for you guys... so I guess props for us to have made it "configurable" eh?
Click to expand...
Click to collapse
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Interesting theory. But I read elsewhere that amazon claims the output of the HDMI socket of the Kindle Fire HD 8.9 would be FULL HD.
I think that the output is in fact 1920x1200 (equaling the native resolution of the kindle display) and thus even MORE than full HD, which is only 1920x1080. And my TV is trying to sequeeze the full 16:10 information into the 16:9 screen and as a result has to display two vertical black bars left and right. So I am looking for a way to actually REDUCE the output of the HDMI socket to the lower (HD standard) 1080 instead of 1200 pixels.
Well I seriously have doubts about this working on amazon's stock os, but supposedly the full version has experimental support for HDMI resolution changing. Give it a shot, though if it doesn't work on Amazon's os I'm more so convinced it will on cm. https://play.google.com/store/apps/details?id=com.nexter.miniscalerfree
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Same Issues
I actually have had very similar problems using my Sony television. I'm curious if you ever found a solution.
stunts513 said:
Well I seriously have doubts about this working on amazon's stock os, but supposedly the full version has experimental support for HDMI resolution changing. Give it a shot, though if it doesn't work on Amazon's os I'm more so convinced it will on cm. https://play.google.com/store/apps/details?id=com.nexter.miniscalerfree
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
My Kindle is rooted, so maybe it works. Thank you very much for the great tip.
I asked the question in the ROM-AOSP CM10.2 forum, since they even have a line under features saying
"HDMI video out is now correct and work across several resolutions. YMMV"
but so far nobody in that forum cared to answer...
I will try out your tip asap and report the results here.
Still I am wondering why I only found so few hits for this issue including in the amazon.com kindle discussion forum.
If nobody uses their kindle to connect it to their TV, why is amazon selling their own branded version of MicroHDMI-HDMI cables?
Ok. Time for an update. I think I am a step closer to a solution.
First I tried the app "Resolution Changer Lite" as recommended by stunts513. In theory it looked great. I was able to select a resolution 1920x1080 and as a result the kindle had a black bar at the bottom and only used 1920x1080 of the 1920x1200 pixels on its display.
So full of expectation I connected the Kindle with my TV. Unfortunately the TV still displayed black bars to the right and left but in addition now also a black bar top and bottom. So while it indeed reduced the displayed area, somehow the Kindle seems to still send the 16:10 information throught the HDMI port, making my TV scale down the picture. I tried all kinds of settings and resolutions to no avail.
As a next step I bought the full version of "Resolution Changer", because it was talking about an additional HDMI feature. Again full of expectation I started the app. Instead of selecting one out of several preset resolutions (like 1920x1080 or 1280x720) the app allows you enter any values for Width and Height. I again tried 1920x1080 with the exact same result as in the lite version.
But the full app has a second tab called "HDMI" and I did the same thing there. Unfortunately again to no avail. After some testing and reading of the description I came to the verified conclusion that all this additional feature does is DETECT if somebody connects a HDMI cable to the port of the Android device and then AUTOMATICALLY changes the screen resolution to the values chosen. So instead of having to invoke the app manually every time you in theory just set the wanted values on the 2nd tab and any time you plug in your TV your android device switches to the defined resolution.
Unfortunately there is no value to edit to stop the Kindle from sending out a 16:10 information to the TV or the app maybe doesn't even change anything that is sent to the HDMI port, but only influences the built-in screen.
But then unexpectedly Amazon's Customer Service sent me a message! They basically confirmed that if you connect your Kindle to a TV through HDMI it sends out it's 16:10 resolution and thus makes your TV scale down the picture.
BUT when you switch to the NATIVE INTERNAL VIDEO APP, the signal sent to the HDMI port automatically switches to 1920x1080 and a 16:9 ratio information. So as a result the native amazon services like "instant video" or other streams will be displayed without any bars. They claimed to even had it tested on a LG Full HD Plasma.
THIS EXPLAINS WHY MOST PEOPLE DON'T HAVE ANY PROBLEMS and thus you can't find much about in the forums.
I have to say I was sceptical, but since I had only used VLC so far to play back the movies, I now used the original video player. And to my surprise the black bars left and right went away and I had a full screen picture!!!
That's why I am saying, I am one step further!
Unfortunately this only helps me partly. For starters VLC plays a lot more formats than the native video player app. In addition I like to watch the movies with subtitles since I am not a native english speaker. VLC plays them automatically if the .srt-file is named the same as the movie itself, but of course the native video player doesn't. I don't even know it is capable of that.
Anyhow the big questions I have now:
1. does somebody know how to make the regular android Video Player display subtitles for example in the format .srt?
2. is there an option in the Android version of VLC (I don't think so, since it is still BETA) to configure the HDMI output?
3. Now that we know, that the regular Video Player can influence the format sent to the HDMI port, is there an app to set the HDMI output permanently to 1920x1080 and more important 16:9 ?
Again any help appreciated...
Ah, I wish I had known you were using vlc I would have suggested a few things. It didn't occur to me you might be using it because I got my from the play store, but it said it wasn't available in the USA, so I had to proxy through another country to get it. Anyways, I know in vlc's options there's a few different output methods, though I don't think that will affect it. Another thing I was thinking of is in vlc, u can change the aspect ratio, I believe the button is on the bottom left above the playback bar while playing a video, when u tap it it switches they various modes, don't know if this will affect the HDMI at all though, as I don't have a minihdmi cable because most of my TV's are CRT, only 2 of them have HDMI plugs, and of those 2 only one has 1080 capabilities, and its a PC monitor so it has no sound output.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Hashcode's CM10.1 and HDMI 1920x1980
Hi Tronar,
Saw your post (http://forum.xda-developers.com/showpost.php?p=45044803&postcount=579) but I'm not allowed to answer in that thread.
I have Hashcode's CM10.1 (20130812) running on my Kindle Fire HD 8.9. I connected the Micro HDMI port to my Samsung Full HD TV, and also saw the 2 vertical black bars (about 2 cm). Using apps like Resolution Changer doesn't help, as I get some weird screen flipping, turning landscape into portrait.
Cheers, S
stunts513 said:
Ah, I wish I had known you were using vlc I would have suggested a few things. It didn't occur to me you might be using it because I got my from the play store, but it said it wasn't available in the USA, so I had to proxy through another country to get it. Anyways, I know in vlc's options there's a few different output methods, though I don't think that will affect it. Another thing I was thinking of is in vlc, u can change the aspect ratio, I believe the button is on the bottom left above the playback bar while playing a video, when u tap it it switches they various modes, don't know if this will affect the HDMI at all though, as I don't have a minihdmi cable because most of my TV's are CRT, only 2 of them have HDMI plugs, and of those 2 only one has 1080 capabilities, and its a PC monitor so it has no sound output.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Well, plenty of stuff to respond to.
First of all VLC was available in the regular Kindle Store. So I didn't even have to root my phone and install the Google Playstore to be able to install it.
In addition VLC is still beta. The configuration options are quite minimal compared to the PC version.
And of course I tried the various screen size and ratio options in VLC. But they only affect the way the Kindle display of 1920x1200 is used, i.e. how the available pixels are filled with the video. So you can achieve all kinds of effects using only part of the Kindle display. But whatever option I chose, the black bars left and right always remained on my TV. To make it simple all I could do was further add more black bars by shrinking the image or distort the image by changing the ratio. None of it seems to have any influence on the HDMI output. I think it is a very special option or feature, the regular Kindle Video Player is using there and would have to implemented explicitly in the VLC player.
Nonetheless this gives me the idea to send some feedback to the VLC developers to add this feature to their wish list. :good:
Anyhow, I really appreciate your help. Please keep the good ideas flowing.
smeitmeister said:
Hi Tronar,
Saw your post (http://forum.xda-developers.com/showpost.php?p=45044803&postcount=579) but I'm not allowed to answer in that thread.
I have Hashcode's CM10.1 (20130812) running on my Kindle Fire HD 8.9. I connected the Micro HDMI port to my Samsung Full HD TV, and also saw the 2 vertical black bars (about 2 cm). Using apps like Resolution Changer doesn't help, as I get some weird screen flipping, turning landscape into portrait.
Cheers, S
Click to expand...
Click to collapse
Well, it seems like nobody is allowed to answer in that read, because so far I haven't received any answer.
Neither in the CM10.2 nor in the CM10.1 thread, where there seems to be at least some kind of life.
Thanks for confirming that the Resolution Changer doesn't help on the CM10.1 ROM. That saves me hours of work of trying out that app on this ROM.
But my question was actually a little more specific. The first page of the thread states under Features:
"HDMI video out is now correct and work across several resolutions. YMMV"
I was wondering if that means that there is some way in this CustomROM to change the resolution of the HDMI video out signal.
Update:
I tried the App "MX Player" to see, if that app would behave more like VLC or more like the native Video Player.
I don't know if I should laugh or cry, but this is what happened:
I started a movie using the freshly installed MX Player and was happy to see, that the subtitles were showing on the Kindle Display. I connected my Kindle with the Micro-HDMI-Cable to my TV and was also happy to see that the vertical black bar were NOT showing, but instead it was using the full resolution of my TV. I was totally excited. And then it hit me:
While the subtitles were showing on the Kindle screen, they were NOT showing on my TV!!! Otherwise both screens showed an identical picture, but the subs were missing.
So I tried out all kinds of options in the subtitles settings. To no avail.
Then I tried switching from using the Hardware accelleration to Software accelleration. The app offers three modes called SW, HW and HW+
And here comes the funny part:
When I switched from any of the two HW modes to the SW modes, suddenly my TV was showing the subtitles. And for a moment I was like "Yeah, I finally found the solution". And then it hit me: now my TV was showing the vertical bars again.
My conclusion from this test:
When you switch to software acceleration, MX Player behaves like VLC. You get the subtitles on your TV, but you have to live with the vertical black bars effectively reducing the resolution.
When you switch to any of the two hardware acceleration options, MX Player behaves like the native Video Player and gives you the correct 16:9 1920x1080p output on the HDMI-out. But for whatever reason the subtitles are only displayed on the Kindle screen and not on the TV any more.
My guess: by using the HW acceleration, the app automatically triggers the built-in feature of reducing the resolution from 1920x1200 to the standard 1920x1080 on the HDMI-out. Apparently amazon has built in that feature into the Hardware acceleration of the Kindle.
I don't know why this kills the subtitles. Either it is a bug in the app or for some reason the Hardware acceleration does not allow the blend-in of the subtitles over the video.
And when you switch to SW acceleration, the Kindle apparently thinks of the app like any other standard app and sends the full 1920x1200 resolution not only to its own screen but also to the HDMI-out.
It would be great to know, if superimposing subtitles is technically impossible when using the HW acceleration because the Kindle chips do not support that at all or if it could be achieved with the right algorithm.
I am unsure if it is the exact same thing offhand but vlc has an option to enable hardware decoding, if it is the same thing try it and see if vlc works . also I don't know much bout HDMI, but if its a digital stream and subtitles aren't showing up, try enabling captions on your TV and see if anything happens, I would think that they would be part of the digital stream in one way or another.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Thank you for the tip with Hardware Decoding option in VLC, but unfortunately it doesn't seem to make any difference. The picture remains shrinked with vertical bars left and right, no matter if you enable that setting or not. The subtitles also remain visible in both settings.
So my guess is that the current VLC beta isn't really enabling the Hardware Decoding on the Kindle. At least not the way, MX Player and the native Kindle Video Player seem to do it.
About the subtitles still being part of the digital stream in the HDMI output: sounds like a great idea as well.
So I tried it out by activating the subtitle setting on my TV. Unfortunately to no avail. It MIGHT be, that the way US-TVs receive and display subtitles from TV broadcasts is different than the one used in Europe (here subtitles are sent through a quite old system called Teletext oder Videotext (depending on the country)).
Or it might be, that the HDMI protocol just does not support this way of transfering subtitles to the TV.
In any case, unfortunately I am not any closer to solving the issue.
But thanks for the good ideas and tips, please keep them coming as I will keep attacking that problem.
Not sure if my issue is Kodi related or Fire TV related, but 3D MKVs (1080p SBS) do not work well on my Samsung TV in 3D mode through Kodi. They do display in 3D once I change the TV into that mode, but there's ghosting. Playing the MKV using the TV's built in Media Player has always worked fine. I suspect Kodi isn't converting the SBS video completely correct. OTOH, I had to calibrate the Fire TV due to my TV's overscan, so perhaps that has something to do with it? I'm not sure. Does anyone have any tips for getting 3D video to work?
You´re TV is using additional filters etc. when the playback is run internally but the TV does not use these for external input via HDMI. It´s most likely you would see this also with other external players.
Concerning overscan: when you don´t need it (for e.g. you´re not using any analogue video inputs), set it to 0 in you´re TV or deactivate overscan. It´s the better solution than to calibrate all attached devices for overscan which isn´t needed for digital HDMI input normally.
Calibaan said:
You´re TV is using additional filters etc. when the playback is run internally but the TV does not use these for external input via HDMI. It´s most likely you would see this also with other external players.
Concerning overscan: when you don´t need it (for e.g. you´re not using any analogue video inputs), set it to 0 in you´re TV or deactivate overscan. It´s the better solution than to calibrate all attached devices for overscan which isn´t needed for digital HDMI input normally.
Click to expand...
Click to collapse
That's interesting because I have two different TVs connected through HDMI that both required the image to be reduced 2-3% with the Fire TV. That ought to be digital. Am I missing something?
EDIT: Okay, here's what I was missing. Both TV sets were NOT set up to the optimal screen settings. The Samsung was set to 16:9, which you'd think would be the right setting, but it's not. The "User setting" with the option to move the picture horizontally and vertically is the "correct" one to use. On the other TV that I was using overscan on had a similarly poorly worded option called "Fullscreen 100%" or something like that that gave the actual resolution instead of the default "Normal" setting. Unbelievable!
The happy ending to this story is that 3D movies work perfectly. I hear there is a plugin for Kodi to automatically switch the TV into the correct 3D mode assuming the MKV file has the 3D encoding option specified. (I went through and fixed all the MKV metadata to include it.) I'll try to find it and test it out.
Those overscans mechanism do imply scalers which may also corrupt the proper displaying of 3D content. I wonder why still today TVs are preprogrammed with overscan for digital inputs.
But you´re 16:9 issue isn´t clear for me. A 16:9 TV should display everything at 100% or is it a non 16:9 TV, for e.g. with 21:9 aspect ratio? In that case the TV probably tried to stretch the 16:9 content instead of letterboxing which may also lead to a bad 3D behaviour.
Calibaan said:
Those overscans mechanism do imply scalers which may also corrupt the proper displaying of 3D content. I wonder why still today TVs are preprogrammed with overscan for digital inputs.
But you´re 16:9 issue isn´t clear for me. A 16:9 TV should display everything at 100% or is it a non 16:9 TV, for e.g. with 21:9 aspect ratio? In that case the TV probably tried to stretch the 16:9 content instead of letterboxing which may also lead to a bad 3D behaviour.
Click to expand...
Click to collapse
The default option on my Samsung 55" TV is "16:9". There's also "Wide" (4:3 stretched to fill the screen) and "Zoom" (4:3 zoomed so the top and bottom are cropped). It's not until you go to the "User" option that you realize that the default "16:9" option (the first setting) is actually zooming the image 2-3%! I can only suspect that Samsung assumed people would be watching a mix of analog and digital sources. You'd assume the cable company's box would take care of any issue with displaying analog signals to a digital TV, but I guess not. The moral of the story here is to not assume the TV isn't implementing an overscan on ALL signals by default.
EDIT: Apparently, my TVs are the only ones like this: http://www.engadget.com/2010/05/27/hd-101-overscan-and-why-all-tvs-do-it/
I have my rooted FTV Stick connected to an HDMI 4 port switch with an HDCP compliant HDMI to VGA adapter to use with an older HDTV that I have which supports various resolutions.
480p / 720p / 1080i for TV resolutions and various PC resolutions
The panel is actually 1024x1024 native but in a 16:9 physical layout
If curious it is a Phillips 42" 42FD9954/69S http://pdfstream.manualsonline.com/3/3c352b8a-cf36-41a1-a84b-4401ab549765.pdf
The HDMI switch I'm using is this one: https://www.monoprice.com/product?p_id=4088 which I've used together with the HDMI to VGA adapter since day 1 (bought them at the same time).
I have the Monoprice version of http://www.amazon.com/dp/B00ZP4H5VI which I've been using for years, with many components running all sorts of resolutions without issue. (PS3, PS4, 360, AppleTV 2nd Gen, standalone BluRay players)
So now I decided to connect my Fire TV Stick to this TV.
FireTV Stick -> short amazon port extender -> HDMI switch -> HDMI to VGA / RCA audio -> VGA & RCA audio connected to TV.
The problem is that the FireTV doesn't allow me to choose my resolution, the TV sees the signal as 640x480 and the resolution menu is forced to 'auto' and if I attempt to pick an alternative resolution (like 720p which I know looks perfect on this TV) it just says "not supported".
I've tried using the adb shell to adjust this but I'm getting nowhere really.
The rest of the internet claims that changing these options will change the resolution being used, well that is not entirely accurate...
This changes the way the device scales the image, but does nothing to affect the actual output
$ wm size
Physical size: 1920x1080
$ wm density
Physical density: 320
Using these settings gives a mostly usable experience but the TV is still getting 640x480 output so as you might imagine things aren't exactly perfect. The main problem is that some apps are hardcoded to a certain density and size. Hulu for example is horribly broken when you change these (even after reboot) but netflix and kodi have no issues.
[email protected]:/ $ wm size
Physical size: 1920x1080
Override size: 1280x720
[email protected]:/ $ wm density
Physical density: 320
Override density: 240
On the plus side, lowering these values seem to increase the amount of free RAM according to kodi's info.
(these settings on my FTV2 actually give me ~840MB of free RAM, vs ~790MB free when at stock settings, running 2880x1620 (3K display setting) shows ~720MB free, clearly as my display is only 1080p there is no way the firetv is actually changing to that resolution, its just scaling it)
The changes don't need root and survive reboot, and you need to kill the app(s) you have open when you change this otherwise their display will be a bit more funky than if you don't restart them.
tl;dr
Stick is output at 640x480 any one know how to get it to output 1280x720p?
the bootloader seems to briefly output @ 1080p (which my display freaks out a bit to as it can't do 1080p but can do 1080i/720p) and then once the Amazon logo is gone and it shows FireTV Stick then it changes output down to 640x480p.
Really annoying as this is the only device that has any issue here. I even bypassed the switch and small extension cable that came with the stick.
I did find the amazon HDMI in ADB shell settings ... however I'm still stuck with 640x480. My only thought is that the signal must be getting recognized incorrectly by the HDMI -> VGA adapter.
I tried the FTV2 with this adapter and hit the same issues, so there has to be something with the adapter or android devices in general that is causing this issue (as every other device works perfectly fine).
If someone in the future needs to get their resolution fixed they can change this setting and reboot:
$ adb shell
$ settings get secure amazon_settings_hdmi_resid
16 = 1080p @60hz
4 = 720p @60hz
-1 = auto (I believe)
$ settings put secure amazon_settings_hdmi_resid 4
$ reboot
(that will change the display setting to 720p)
My FireTV stick is running 5.2.1.2 and it seems Amazon has (re)moved the setting amazon_settings_hdmi_resid. Anyone know how to list all available settings? Having the same forced resolution of 640x480.
I am thinking on buying this phone, I would use it as a "laptop" occasionally on holiday trips - connecting kb and mouse and external monitor. How about scaling on mirrored screen? I have tried MHL cable with my fullhd Sony Z2 with a fullhd monitor and it just mirrors the screen. It is not smart enought to get things smaller on a larger screen ie. the icons are huge on monitor, office tools and sheets are too small on mobile screen and so is on the monitor, it should instead be scaled properly. Does anyone know does ti scale properly or that is the problem with android? Look at this for example http://www.winbeta.org/wp-content/uploads/2016/02/HP-Elite-x3-Dock.jpg I am not MS fan or I want to buy MS phone but this scales as it should. If someone tried please do post a result.
The MHL cable won't work for the Note7, unfortunately, but I believe there are other methods for directly connecting it (DisplayLink?).
In any case, the phone won't natively scale like you want it to - but there's an app that will do that for you called Andromium OS. Download that and it should be what you're looking for.