Join Date:Joined: Dec 2007
Just my Two cents...Rooting will help only in regards if Google rejects MX's Receiver app from being whitelisted...(really no reason they would do that though so it's kind of moot.) There is one way it could help but it's complicated, will get back to that point later on.
As to the other questions regarding containers (like MKV)...
I believe that is all handled by the receiver app and not limited to what Google supports via hardware.
The Specs google lists do not include DHT but Netflix supports that codec, (Containers are much easier to support than Codecs.)
Two reasons for that, 1) Their player is customized to receive their encrypted streams and they have plenty of money to license whatever codecs they choose to support...
and 2) their Receiver App does not work in the same limited sandbox space all other Receiver apps work in. It also doesn't get the Netflix App over the Internet it is built into the OS which is probably a key requirement to avoiding being put in that sandbox.
But there is nothing to stop a receiver app from providing software support for various containers or codecs.
As to the Root Hope I alluded to...
It is possible that an IN OS Player receiver could be included in the custom rom rooted users are running in the same way Netflix is included in all the official Google Updates.
And it's possible that it could be loaded outside the sandbox in the same way Netflix is.
Since Team Eureka controls the Rooted Whitelist they could add the MXCCast Receiver and load it the same way Netflix is loaded.
Not sure the Dev has that type of thing in mind and not suggesting they should try to implement in that way.
Chances Google would accept that type of system working that way are slim to none...
But it would reduce the need to transcode using the Mobile device and make MX work more like a Local Netflix.