[Galaxy Note 8.0 (Tablet) General] gooberdude:
Dirty fix without replacing files.

Thanks for both of your replies... Jazzespresso, I am not a developer and because of it, I think the peeps who frequent here find my posts interesting for thought for the most part. I have two issues to why I am not active in posting my personal fixes as packages. One, too many find issues to why something may break and will expect expertise. The later is I have yet to make a proper package, as every backup I make on the 4.4.2 device soft bricks the device once flashed. So, if any thing being snake bit by my own hand makes me even more shy about giving out anything that I touch upon in making changes.

Now for a great addition to tweaks for the best image quality and playback with allsharecast.

I perposfully made this wordy, so if anyone should attempt, will be informed of what this tweak does and have an understanding of what it affects and how to assess what they are doing. Remember, I did not tell you to do anything, just gave you enough to look into what can be done.

Because I have no ability to push beyond 72mbs on my wireless router with my tablet, I have a limit to how smooth my allshare up and video down streams can work together. I am bottle necked at 40000000 bps with allsharecast. So I would assume 30000000 bps is at the edge of my video downstream with 90 % of the apps I use.

Until recently I checked out Directv sports streaming via allsharecast, and noticed how choppy and blurry it was. Obviously when pushed at the limits of my wireless router connection, audio only would play back or no connection what so ever. Directv live streaming seems mostly effecting sports not programmes or ads in the sports channels.

I figure the live material is true 720p @ 60fps, which taxes the abilities to allsharecast. The device is native 30fps on both HDMI and Allshare, so it has to do twice the work to make an image. Now for the kicker. Directv throttles stream directly, so no caching of data for you. Since the CPU/GPU has to throttle along with the data stream there is a sync delay being made during the process, in which allsharecast cannot work around. The only work around is to push very close to 2x the data as it is factory set for.

Why so much data... Well because you want allsharecast to take what is given by the app to decode into live packets without having to readjust the image to compensate for higher than expected data rates. Each resolution has a specific data rate to transmit or cast out to the WIDI display device. You will see that in the WFDConfig.xml file... that depending on the device that is connected via allsharecast will allow a particular data stream, governed by an option bit. The option bit or bits will select the maximum and any other data stream that it can handshake. The funny thing is, since android does not request the exact min / max values from its connection, it gives a best guess depending on the option bits it reads from the device, as it expects the device to be compliant. Are all devices compliant??? Coming from China and what not... No.

Because most do not know the capabilities of their wireless display adapters or devices, it will be random at best for them to select which area to tweak to allow a higher than maximum value in the xml file. Thus one must perform a shot gun method of hitting as many possible valid settings at once. Leaving the low bit rate values alone as they are a waist to deal with. Though there is a catch... some devices may have odd bits, that do not reflect their capabilities to android, so android may make the wrong guess and push a lower quality bit rate than what the device can deal with. Or in worst case, higher than what the device can operate with, and get no picture or fail to connect display after obtaining IP.

Now that that info has been stated, if by change during the tweak, you find the picture quality less than expected or no connection... that the changes you made must be changed to compensate for going the wrong way.

Now what can be done, as we all think data is compressed all the time, in allshare, WIDI and what other format, the data stream is uncompressed unlike the data stream sent from the servers. It all depends on ones dongle, tellie, or display with miracast capabilities may not have the ability to go beyond 45000000 mbs. Only testing can be done with what ever device you own.

I tested my dongle as it is HDMI 1.4a compliant, and found for a brief moment I was pushing 50000000, until the download stream failed to cache enough for playback. So until I am able to replace my 10 year old DSL wireless router that is being used as a gateway to my DOCSIS modem, I will never be able to test the limits of what my tweaks can do.

I will give only giving out the settings I am using, and not the file as it is modified to the point of being of use for only one of many various Miracast dongles you can find on Ebay. All I can say about the dongle is that it uses the latest firmware (V 5.0.0 - RC2) which I was able to download and flash.

I have realized every app that streams video from the internet uses different streaming techniques and perform stream caching on their own, while others allow Android to perform the task of data caching. As we see more efforts in making faster and larger data packets in streams, we'll see more and more play back issues with KK and LP because newer techniques are expecting real-time decompression during playback. Probably due to copy write protection, as the data is not stored in any way.

In order to fully test my allshare tweaks for KK, you must remove or # any and all build.prop tweaks associated with data and wifi tweaks. Also freeze or remove any app that helps with internet speeds.

Once you are done cleaning up... open the WFDConfig.xml file in the system/etc folder.

If using a device with native 800 x 1280 display make sure the Horizontal res and vertical res is set at 1280 and 720 respectfully. There is no reason why you want Allsharecast to upscale to the default of 1920 x 1080 when all it does is consume battery and cpu / gpu resources to make the best playback possible. This will allow for smooth and reliable wireless display playback under the most demanding material or live streams.

Now for the fun part... meaning you must do the dirty work of finding where to go or just change everything in regaurds to minimum and maximum values ... blah blah blah

I played with drop frame value and others... the only noticeable benefit being limited with my max bandwidth of 72mbs, was to disable MacroBlocks by setting it to 0. This helps a lot with data streams that are not cached.

Now for the values that will boost image quality.

I have successfully tested connectivity and playback with a 30000000 bps MinBitrate and am limited at 40000000 bps at MaxBitrate.

Right now the bigest trouble is with Hulu studdering with movie playback. Once that is corrected with a better app, allshare cast will play back what you see on the tablet screen. I think once someone tests with at least 75000000 bps as MaxBitrate with a 50000000bps MinBitrate, as long as their device can support 80000000 bps and above, Directv will allsharecast without any issues. As seen in my testing, playback via wireless has cleared up substantially, and can watch Hocky and Tennis with synced audio, as before it was not able to. Though there is some skippy and blur, the playback is functional over being unbearable.