HDR Content not Displaying Correctly - Nvidia Shield TV & Shield TV Pro (2019) Questions

I bought this to replace my Roku Ultra. With that said, the same TV, same AV receiver, and the same cables all play HDR content perfectly fine. Only replacement is Roku to Shield.
The TV will see an HDR signal when it's fed one (whether from local media or online (e.g. Netflix)). The TV menus are really bright and going under settings I can see it's showing HDR or Dolby Vision when applicable however the picture quality of the actual content itself is extremely dull. Best way I can explain it is try to play an HDR video on an SDR screen. It's extremely washed out.
Any thoughts? I've set it to color match Rec.709 and Rec.2020 and also it detects as a HDR10/Dolby Vision 4K ready TV on the Shield.
While my other hardware shouldn't matter since it works on the Roku this is what I'm feeding it through.
TV: Sony XBR75X940E
AVR: Yamaha RX-A1060 Aventage

I read there was a bug in the color match function on the new Shield. Do a Google search for a story about the hot fix. It's only being pushed out at first to owners that request the update on Nvidia's support page but will get a wide rollout in the near future.

jhs39 said:
I read there was a bug in the color match function on the new Shield. Do a Google search for a story about the hot fix. It's only being pushed out at first to owners that request the update on Nvidia's support page but will get a wide rollout in the near future.
Click to expand...
Click to collapse
Oh trust me I have before I resorted to posting on here. Yes that fix they pushed out does fix the HDR color space issue I described above.

Nosferatu. said:
Oh trust me I have before I resorted to posting on here. Yes that fix they pushed out does fix the HDR color space issue I described above.
Click to expand...
Click to collapse
Did you get the hot fix automatically or have to request it?

jhs39 said:
Did you get the hot fix automatically or have to request it?
Click to expand...
Click to collapse
Requested it. It's not for public release it says in the "What's New" section so I doubt it was pushed to everyone.

This originally posted back in November (Nov 4-8) and wondering if the hot fix was released as a general patch/update to the public, or if this is still something that is happening to new devices today? I just purchased a new Nvidia Shield TV Pro (2019) and have not received it yet. Wondering if I will have similar issues once I install it.

https://www.nvidia.com/en-us/geforc...9-shield-experience-upgrade-810-hotfix-image/

Nosferatu. said:
I bought this to replace my Roku Ultra. With that said, the same TV, same AV receiver, and the same cables all play HDR content perfectly fine. Only replacement is Roku to Shield.
The TV will see an HDR signal when it's fed one (whether from local media or online (e.g. Netflix)). The TV menus are really bright and going under settings I can see it's showing HDR or Dolby Vision when applicable however the picture quality of the actual content itself is extremely dull. Best way I can explain it is try to play an HDR video on an SDR screen. It's extremely washed out.
As an aside, I also feel the Shield is transmitting a slightly brighter/better HDR image than the Roko Ultra did with Netflix and Prime Video. That is a subjective comment but I strongly believe that is what I'm seeing.
Any thoughts? I've set it to color match Rec.709 and Rec.2020 and also it detects as a HDR10/Dolby Vision 4K ready TV on the Shield.
While my other hardware shouldn't matter since it works on the Roku this is what I'm feeding it through.
TV: Sony XBR75X940E
AVR: Yamaha RX-A1060 Aventage
Click to expand...
Click to collapse
I've also just upgraded from a Roku Ultra to a NVIDIA Shield (2019) tube. I have a Optoma HDR10 4K projector. I noticed something that you may want to consider. My projector was set up to automatically use a HDR image profile (image settings) when a HDR signal was detected. When I started using the new Shield my projector's HDR image profile was not being triggered and the image had a washed out look to it. I could manually force the projector to use the HDR image profile but it was a hassle but one I could live with.
After applying the Hotfix which corrected the color matching issue I did some other playing around with the Shield's display settings. All of a sudden the projector was recognizing HDR content and auto switching to the HDR image profile settings. I don't think the Hotfix had anything to do with this change but I wanted you to know I also have the Hotfix installed.
My Shield's display setting is ""4K 59.940Hz HDR10 ready" with my projector seeing the input signal as either 4.2.0 10bit BT709 SDR 59.940Hz or 4.2.0 10bit BT2020 HDR 59.940Hz when a HDR10 source is being transmitted from Netflix, Prime Video and Plex.
Just maybe you can try various Shield Display settings (HDR READY ones) and one of them will work better with your display device as it has in my case.

3DSammy said:
I've also just upgraded from a Roku Ultra to a NVIDIA Shield (2019) tube. I have a Optoma HDR10 4K projector. I noticed something that you may want to consider. My projector was set up to automatically use a HDR image profile (image settings) when a HDR signal was detected. When I started using the new Shield my projector's HDR image profile was not being triggered and the image had a washed out look to it. I could manually force the projector to use the HDR image profile but it was a hassle but one I could live with.
After applying the Hotfix which corrected the color matching issue I did some other playing around with the Shield's display settings. All of a sudden the projector was recognizing HDR content and auto switching to the HDR image profile settings. I don't think the Hotfix had anything to do with this change but I wanted you to know I also have the Hotfix installed.
My Shield's display setting is ""4K 59.940Hz HDR10 ready" with my projector seeing the input signal as either 4.2.0 10bit BT709 SDR 59.940Hz or 4.2.0 10bit BT2020 HDR 59.940Hz when a HDR10 source is being transmitted from Netflix, Prime Video and Plex.
Just maybe you can try various Shield Display settings (HDR READY ones) and one of them will work better with your display device as it has in my case.
Click to expand...
Click to collapse
The Hotfix is no longer needed to correct the issue. Did the Hotfix correct it for me? Yes. However I didn't like being permanently in a beta pathway so I returned that Shield and bought another one. The standard fix that came after the Hotfix also fixed the issue.

Nosferatu. said:
The Hotfix is no longer needed to correct the issue. Did the Hotfix correct it for me? Yes. However I didn't like being permanently in a beta pathway so I returned that Shield and bought another one. The standard fix that came after the Hotfix also fixed the issue.
Click to expand...
Click to collapse
I'm glad to hear your issue has been resolved. One small correction is that the "permanently in a beta pathway " is only permanent until a certified general release including the Hotfixes is distributed. I wouldn't have joined the Hotfix program unless there is a way to control it besides turning off auto updates.
I needed the Hotfix as I was impacted by the color matching bug red shift issues especially with skin tones. Here is a link where the Hotfix in-permanance is confirmed (scroll down until you get to these posts).
BizzyB 2d
Random question. If you go to sign up for the hotfix process it says "There is no way to leave the HotFix process once you join it." Are you signing up for just 8.1.0 hotfixes until the next release, or will you be in the hotfix process in perpetuity?
NVIDIA Staff
[email protected] 2d
Just 8.1.0+

3DSammy said:
I'm glad to hear your issue has been resolved. One small correction is that the "permanently in a beta pathway " is only permanent until a certified general release including the Hotfixes is distributed. I wouldn't have joined the Hotfix program unless there is a way to control it besides turning off auto updates.
I needed the Hotfix as I was impacted by the color matching bug red shift issues especially with skin tones. Here is a link where the Hotfix in-permanance is confirmed (scroll down until you get to these posts).
BizzyB 2d
Random question. If you go to sign up for the hotfix process it says "There is no way to leave the HotFix process once you join it." Are you signing up for just 8.1.0 hotfixes until the next release, or will you be in the hotfix process in perpetuity?
NVIDIA Staff
[email protected] 2d
Just 8.1.0+
Click to expand...
Click to collapse
So you're in the Hotfix until a new OS version it sounds like. I didn't want to be in that boat so I returned it. I have two Shield TVs (one in living room one in movie theater). Once I confirmed the general release fixed it on my other rig I returned the Hotfix unit and picked up another. Not going Hotfix again. At the moment, everything works, therefore I'm in no rush to push any futher updates to the unit.
Only thing I can say is my TV (Sony XBR75X940E) to get the color space to work correctly and all the time I had to put the TV in BT.2020 mode. permanently even for non-SDR content. With it staying fixed in an HDR-based mode the Shield appropriately sends a BT.709 signal (SDR) in BT.2020 format so it seemlessly goes from SDR content at the right colors (YouTube TV, YouTube, Emby content I have in non-HDR) to HDR content (Netflix, Amazon, Emby content in HDR, etc.) in the correct colors.

Related

New video chat/conference software

I ported my ReelPortal video conference to Android recently. It's reported to be working on the Viewsonic G Tablet with certain ROMs, as well as the Archos 70/101.
I had one Samsung Galaxy Tab user reported his device bogged down badly when running my software. Initially I thought it may be because it doesn't have a Tegra-2 cpu, but so is the Archos. So I'm not sure why. Also, currently on Android 2.2, my app can only access 1 camera, and the user reported it was the back camera. The Viewsonic/Archos only have 1 (front) camera, so it works great for them. However, Android 2.3 will provide access to multiple cameras.
Anyhow, I want to see if other Galaxy Tab users can run my app. It is published on AppLibs, or you can get it from the Viewsonic G Tablet thread here:
http://forum.xda-developers.com/showthread.php?t=908613
I suggest test the tablet with another PC/Mac/Linux machine (vs tablet to tablet), so it's easier to figure out problems.
Please provide feedback if you try it. Thanks.
Would love to test this with my linux server, but can't find the download for that on your site. If this works well on my Tab, it might replace my need for OpenMeetings.
agentdr8 said:
Would love to test this with my linux server, but can't find the download for that on your site. If this works well on my Tab, it might replace my need for OpenMeetings.
Click to expand...
Click to collapse
I will release the server executable in a couple days. Right now, you can test the client using my server. Some Viewsonic user was able to do a conference between his tablet and 3 other PC's, and said it works as well as dimdim.
Tested the reelportalX on the Tab and it worked ok. Video was from rear camera only (known issue though), and the interface was a bit slow to respond. It FC'd a few times while fiddling with the camera resolution, and also when initiating a P2P session from my netbook to the Tab.
agentdr8 said:
Tested the reelportalX on the Tab and it worked ok. Video was from rear camera only (known issue though), and the interface was a bit slow to respond. It FC'd a few times while fiddling with the camera resolution, and also when initiating a P2P session from my netbook to the Tab.
Click to expand...
Click to collapse
Curious...can you try the web client (via browser) on the tablet, to see if the interface behaves the same? note: the web client can't access camera/mic on the tablet, but it can do everything else. If its different, then perhaps AIR somehow runs slower than Flash. If not, then I guess it's just slow .
Sorry I don't know what FC'd means. Crashed? For camera resolution, I suggest sticking to standards like 640x480, 320x240, etc. Other non-standard resolutions could mess things up (codec, driver). But I don't think the tablet can handle 640x480 encoding (while also decoding incoming streams).
BTW, did the netbook crash too?
FC = Force Close. The default resolution was 320x240 @6fps, and it seemed ok, although it never updated the image on the Tab (seems like it took a static picture, not streaming constantly).
The netbook was fine. It's running Win7 and I tested it with Firefox 3.6.13 on a Lenovo Ideapad S10-3.
Running the browser on the Tab and going to reelportal.com seems to work fine, without camera of course.
agentdr8 said:
FC = Force Close. The default resolution was 320x240 @6fps, and it seemed ok, although it never updated the image on the Tab (seems like it took a static picture, not streaming constantly).
The netbook was fine. It's running Win7 and I tested it with Firefox 3.6.13 on a Lenovo Ideapad S10-3.
Running the browser on the Tab and going to reelportal.com seems to work fine, without camera of course.
Click to expand...
Click to collapse
that's interesting...somehow the back camera is not feeding video streams continuously...i don't think its the cpu then, because the resolution is low...perhaps the camera driver is not compatible with Air...maybe it thinks the software telling it to take a picture, instead of streaming. I didn't have a problem with the back camera on the Droid 2...are you running on the stock ROM or something else?
BTW, is there some other external controls (software) for the back camera on the tablet? Like driver settings on the PC.
I'm running the Euro JME rom (Roto-JMEv4 specifically). There's no special controls for either of the cameras. If you're planning on supporting the Tab, Samsung offers some APIs specific to the Tab for 2.2 development via the SDK which should include front cam support.
Hmm....looks like someone also encountered the same issue...and there's a work around (inconvenient)
http://stackoverflow.com/questions/...py-on-samsung-galaxy-tab-with-air-application

Problems with the 10.1v so far

After playing around with the 10.1v for a couple of days, here are the problems I've come across.
Android Ver. : 3.01
Kernel Ver. : 2.6.36.3-00558-g7c1c334
[email protected]#1
Build number: HRI83.BUKD9
Here goes:
Video playback is pretty choppy [alt. thread]
So far I haven't got any 1080p .mkv files to work. Heck most of my 720p .mkv stutters or doesn't play at all anyway. All are H.264/x264 .mkvs played using either MoboPlayer (with the ARMV7VFP codec update installed) or the default player. I know the literature mentioned that only H.264 Main profile is supported, but come on, my SGS plays those videos fine (except one which has an AC3 track - fair enough).
I'm guessing this is due to the lack of NEON hardware in Tegra 2. Nice job nvidia.
Update: After googling around it seems like there's no built in support for Tegra 2's h.264 decode hardware acceleration in the native Honeycomb libraries (--devs correct me if I'm wrong). There is however, this youtube video showing an unreleased Cyberlink media player doing hw acceleration. Although note that the device he's holding is a Galaxy Tab 7" (which of course, runs Hummingbird, and AFAIK there's no Tegra 2 version in the wild).
Apps have problems with plugged in headphones
This is really weird and annoying. If I plug my headphones to the jack in the middle of a video/audio playback (using both the default player and MoboPlayer), the sound would get routed to the headphones just fine. But when I, say, switch apps, or change media files using the gallery, sometimes the sound would get routed to the speakers even though my headphones are still plugged in. I can fix this by unplugging the headphone (which pauses the video/music) and plugging it back in - but it gets irritating after a while.
No proxy server settings
Important since I'm behind a server which I would really like to be removed but that's beyond my power. The XOOM guys have the problem as well. Just used Proxy Settings from the marketplace and most things would work.
App downloads fails sometimes
Sometimes if I put the marketplace into the background, downloads would continue to 100% but fail to install. Not sure if it's just me though. *Edited*
Browser ALWAYS fails to download stuff through the proxy
Weird really. Every time I clicked "save link as" or a site would try to download something it would fail - but only if I'm behind a server. I try to browse using WiFi as often as I can since I don't have that much quota with vodafone. Note that I am behind a Squid proxy with plaintext authentication (I just hate those stupid admins!) - without the username/password you'll just get HTTP error 407. I can browse using the exact same ports and protocol (HTTP) but can't download through the proxy. I still can't figure that out at all.
The only way I can get around this is by using Opera, and setting the proxy server in manually using opera:config.
No way to force the browser to use a desktop UAString
There's a solution to this apparently, and it works: link.
Contact imports sometimes gets stuck
Importing contacts from a .vcf file sometimes hangs (not force close) the contacts app. I exported my contact list from my SGS (had about ~112 contacts with disp. photos and multiple numbers in some of them) and put them in the Tab, and had to import 3 times. What's worse, I ended up with duplicate copies of the same contacts. So I figured out the easiest way of doing this is to delete the whole contact list and start again, but---
---There's no way to delete multiple contacts at once. I spent like 2 mins deleting contacts one by one.
Update: Solution: Sync contacts via your Google account. Thanks pegaxs for pointing this out.
Marketplace automatically switches screen to landscape mode
This annoys the hell out of me since I usually browse in potrait mode - the device feels a lot nicer that way. Whenever I launch the market, it rotates itself. Minor thing, but annoying. Okay, I'm nitpicking.
On top of those - only 1 usb cable (which wouldn't be a problem if it can be charged using USB ports in the computer), and a short cable at that. wtf.
Fyuh. Rant finished. For now.
Can someone confirm these on their tab as well? I can't seem to find any updates at all.
There's also no WhatsApp, Adobe Reader (the QuickOffice HD works, so not really a complaint), or a text messaging app (but curiously you can send an SMS to it and read it by sending it to your broadband number - it'll appear under Service Info. I haven't tried MMSing yet, but I tried calling to it. It just hangs up (with a busy tone).
Add to that list "backlight bleeding". Watched some videos last night for the first time (re-encoded some 720p mkv because they wont play) and noticed a lot of back light bleeding along the lower edge and along the right hand edge. Probably would not have been as bad or noticable if the video played at full screen. It only plays up to the limit of the buttons in moboplayer. The built in player plays full screen... BUT... wont play native divx/xvid.
And yes, have to agree... that USB cable could have been a little shorter... OMG! how bad is it. I know the size of the battery wont allow it to charge off the computer USB, but i have to put my tab on the floor to reach. Going out to buy a USB extension today...
The SMS thing seems to be a honeycomb issue, as all the Xoom guys are complaining as well... I cant find any settings for it anyway, as there is on say, the phone version of android. It is a bity sad that apps like "whatsapp" cant be used in it's place. I have seen a post somewhere saying "textfree" might work, but it is most likely restricted to US markets as it gives you a US phone number to SMS to.
As for importing contacts, i just sync them to the Google account and they come up on all my devices. No moving files around, or importing/exporting... just sync to gmail and on the next sync, any device you have linked to that account will be updated with the contacts list.
I hope a lot of the issues OS wise, like adobe acro reader and mkv/divx support will be updated in the next version of Honeycomb, like it has been developing on phone android. Maybe when twiz is released for the samsung tab, it might bring with it more of the same functionality as the Galaxy S phone does. The phone seems a better candidate as being a tab then the 10.1v does
interested to see where it goes from here... I can see it's not perfect, but i can see it isnt a bad start and it has so much more potential to improve
I feel like the volume up/down buttons are the wrong way around? i.e. the volume control button nearest the unlock/lock button is volume DOWN and i feel like it should increase volume?
Also when i press unlock the screen takes roughly 1 second to light up
(not huge issues, but little things that would seem easy to fix)
How bad is the backlight bleed? I haven't seen anybody else mention it on the Samsungs. I did just learn that Samsung doesn't always use their own panels in their products. They also seem to use different parts in the european products vs. the US counterparts.
Considering all the hoopla over the iPad 2 and the backlight bleed, I would think manufacturers might be a bit more cautious. Apparently that problem was due to LG, who Samsung sometimes uses.
I hope this doesn't turn into another iPad 2 and Asus Transformer problem where it takes fifteen tries to get a decent product.
bbeelzebub said:
How bad is the backlight bleed? I haven't seen anybody else mention it on the Samsungs. I did just learn that Samsung doesn't always use their own panels in their products. They also seem to use different parts in the european products vs. the US counterparts.
Considering all the hoopla over the iPad 2 and the backlight bleed, I would think manufacturers might be a bit more cautious. Apparently that problem was due to LG, who Samsung sometimes uses.
I hope this doesn't turn into another iPad 2 and Asus Transformer problem where it takes fifteen tries to get a decent product.
Click to expand...
Click to collapse
Didn't notice this on a European unit.
pegaxs said:
Add to that list "backlight bleeding". Watched some videos last night for the first time (re-encoded some 720p mkv because they wont play) and noticed a lot of back light bleeding along the lower edge and along the right hand edge. Probably would not have been as bad or noticable if the video played at full screen. It only plays up to the limit of the buttons in moboplayer. The built in player plays full screen... BUT... wont play native divx/xvid.
Click to expand...
Click to collapse
I didn't really notice much of the backlight bleed, but then again I might be too tolerant on that. I've got the display set at like 30%-40% brightness most of the time anyway. I personally think that the bleed is about the same as the Galaxy Tab 7".
pegaxs said:
And yes, have to agree... that USB cable could have been a little shorter... OMG! how bad is it. I know the size of the battery wont allow it to charge off the computer USB, but i have to put my tab on the floor to reach. Going out to buy a USB extension today...
Click to expand...
Click to collapse
I need to get an extra one, since I charge mine next to my bed and the computer is on the other side of the room. I don't want to keep switching cables. I'll give a visit to the vodafone store to see if i can get one. Or just grab one off ebay.
pegaxs said:
As for importing contacts, i just sync them to the Google account and they come up on all my devices. No moving files around, or importing/exporting... just sync to gmail and on the next sync, any device you have linked to that account will be updated with the contacts list.
Click to expand...
Click to collapse
:facepalm: why didn't I think of that
I'm pretty sure the problem is mostly software (well, apart from the backlight bleed), so I'm hoping a future update would clean this up for us. So far I've got the I8000 (good for nothing except playing movies) and the SGS. I9000 and both are excellent PMP devices.
Oh for those curious, there's a way to force the native browser to use desktop UA strings to sites: link It's for the XOOM but I've tried it and it works.
market apps no link
after downloading certain apps when i went back to the market those apps are showing free or $ amount instead of installed is that happening with everyone or just me. dosent look like market is registering my installed apps.
I noticed the same within the market app.. thought it was a feature
Sent from my GT-I9000 using XDA Premium App
When the screen is black and on full brightness it looks horrible about 10% off the screen is lightgrey at best.
When using the device you don't notice it. Unless the edges of the screen are (supposed to be) black, while the brightness is close to Max...
Sent from my GT-I9000 using XDA Premium App
gjroeleveld said:
I noticed the same within the market app.. thought it was a feature
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
I agree, I think it is a "feature" of the Honeycomb Market. If you go to the "My Apps" section of the Market - everything you have downloaded or purchased will appear there, but they just show as "Free" or "$x.xx" when casually browsing for apps - which I find annoying.
My tab works great, the only issue is that I've got extreme backlight bleeding at the bottom and at the right side of the screen, the right side is not much of an issue but the bottom is extremely annoying due to the black. I'm about to return it.
Yes, the backlight bleeding is a serious issue.
I've seen 3 of these devices now and they all have the same extreme case of it.
I'm going to start to start a new thread soon when I have a chance to take some good photos, unless someone beats me to the punch
Heres mine, Vodafone got a new one ordered for me which can take up to two weeks for whatever reason. If it has the same issues I will claim my money back and wait for the thin version.
As to the OP for HD video playing, i was testing the HD capability and found that even with a Xoom its unable to play full 1080 and 720 without recoding them. Thankfully a xoom owner has already done his bit of testing and all you need to do is download HandBrake and import his settings Settings Link. Encoding takes a while but i have tested on 1080p and 720p and they play just fine. File size i took from 1080p was about 15gb and it was reduced to about 2GB or so. You'll still need to get rockplayer as it does HW decoding to make the video play smoothly. alternatively you can use moboplayer but i prefer rockplayer's quality decoding for some reason
I also have some backlight bleeding issue, but only when i turn my brightness all the way up, i generally leave it on auto now and there's no bleed what so ever. I believe someone on WP has already mention that he checked all the 10.1v available in the Vodafone store in his location and they all have backlight bleeding issue and i believe it to be a batch and QA issue.
Other than that its more towards apps not compatible with honeycomb and they tend to force close a fair bit. Even the app market and app list drawer tend to crash often and the uptake to produce 3.0 compatible apps have been very slow from what i see, but hopefully those 5000 people that receive the new 10.1 sexy tab will be motivated to make apps and widgets.

Remove Black Bars on HDMI Output

So I've discovered that a simple terminal command fixes the black bars on the left and right when outputting through HDMI. It's caused by the tablet outputting a 1280x800 display to a 1280x720 signal. This is easily fixed by changing the device's resolution with the following command:
wm size 720x1280
To revert to the tablet's original resolution, use:
wm size reset
You may need to run the "su" command first for these commands to work, and you do need to be rooted in order for it to work. This will cause some things to get wonky, like the nav buttons disappearing in landscape orientation or the status bar being hard to pull down (perhaps solvable with a change to the DPI), but if you're planning to use this trick for gaming (which was my reason), using something like Smart Launcher 2 with a controller makes this a non-issue. If you want a quick and easy way to switch back and forth, try QuickTerminal on the Play Store and set up both terminal commands as "Quick Commands", or at least that's how I've done it. Now, the picture on your TV will fill the screen. This is as close to Console Mode as we'll probably ever see on this device, so I thought this might help a few people out!
rchrdcrg said:
So I've discovered that a simple terminal command fixes the black bars on the left and right when outputting through HDMI. It's caused by the tablet outputting a 1280x800 display to a 1280x720 signal. This is easily fixed by changing the device's resolution with the following command:
wm size 720x1280
To revert to the tablet's original resolution, use:
wm size reset
You may need to run the "su" command first for these commands to work, and you do need to be rooted in order for it to work. This will cause some things to get wonky, like the nav buttons disappearing in landscape orientation or the status bar being hard to pull down (perhaps solvable with a change to the DPI), but if you're planning to use this trick for gaming (which was my reason), using something like Smart Launcher 2 with a controller makes this a non-issue. If you want a quick and easy way to switch back and forth, try QuickTerminal on the Play Store and set up both terminal commands as "Quick Commands", or at least that's how I've done it. Now, the picture on your TV will fill the screen. This is as close to Console Mode as we'll probably ever see on this device, so I thought this might help a few people out!
Click to expand...
Click to collapse
I've been doing something similar with the NOM Resolution Changer app but I can't get the DPI settings right to match the 720x1280 res. It gets a bit tricky getting back into settings etc after changing the res as my app drawer is inaccessible after doing so. I always just resort back to default with the fail safe timer, I really don't want to get stuck in a resolution which i can't get back out of.
Andy4Shurr said:
I've been doing something similar with the NOM Resolution Changer app but I can't get the DPI settings right to match the 720x1280 res. It gets a bit tricky getting back into settings etc after changing the res as my app drawer is inaccessible after doing so. I always just resort back to default with the fail safe timer, I really don't want to get stuck in a resolution which i can't get back out of.
Click to expand...
Click to collapse
I haven't had that probably making the change manually, and I do believe I tried the app you mention and had the same issue, so you might wanna try testing the terminal command out; if it messes up, you can always reboot the tablet and everything will properly reformat for the lower resolution and then you should be able to change it back with "wm size reset".
rchrdcrg said:
I haven't had that probably making the change manually, and I do believe I tried the app you mention and had the same issue, so you might wanna try testing the terminal command out; if it messes up, you can always reboot the tablet and everything will properly reformat for the lower resolution and then you should be able to change it back with "wm size reset".
Click to expand...
Click to collapse
Thanks rchrdcrg, yeah I'll give it a whirl that way. It is really annoying having those black end sections on the output!!
I've got a chromecast and been trying to get the 'cast screen' option to work using r3pwn's method here http://forum.xda-developers.com/hardware-hacking/chromecast/experimental-enable-mirroring-device-t2812193/page167#post55119152
I thought that might be worth a shot to see if the output res remains at 1200 x 800 for the mirror but I can't get a picture to display, only sound, when it connects and tries to cast screen. I'm thinking it probably won't make a difference though as I have just bought a miracast ezcast m2 dongle too and that still displays at the 1200 x 800 resolution when miracast is used. It probably is just a rom limitation at the moment.
Andy4Shurr said:
Thanks rchrdcrg, yeah I'll give it a whirl that way. It is really annoying having those black end sections on the output!!
I've got a chromecast and been trying to get the 'cast screen' option to work using r3pwn's method here http://forum.xda-developers.com/hardware-hacking/chromecast/experimental-enable-mirroring-device-t2812193/page167#post55119152
I thought that might be worth a shot to see if the output res remains at 1200 x 800 for the mirror but I can't get a picture to display, only sound, when it connects and tries to cast screen. I'm thinking it probably won't make a difference though as I have just bought a miracast ezcast m2 dongle too and that still displays at the 1200 x 800 resolution when miracast is used. It probably is just a rom limitation at the moment.
Click to expand...
Click to collapse
Yeah, I "borrowed" a Chromecast from Best Buy and could never get screen casting to work. You might want to see if changing the resolution fixes this issue with Miracast as well... I have a suspicion it will, and that might be useful to some folks. I sure wish I knew how to force the HDMI output to 1080p; it switches over when playing a 1080p video, so I know it's possible, but I don't know enough about development stuff to know how it's doing that, and forcing the resolution to 1080x1920 with the "wm size" command just displays a 1080p picture downscaled to 720p.
try vlc beta off the play store
here's a sort of rant and with a video playback only solution. Not sure how to hide the rant part. I don't forum anything much.
I bought a Belkin miracast adapter off amazon, and have had trouble getting videos playing properly in full screen. It would mirror the 1280x800 with videos played with regular video apps ( MX player, Archos player, stock) which would be 16:10, and would have those bars on either side on both my 1080p insignia tv and our pseudo 720p panasonic (actual res was 1024x768, but at 16:9, which should be illegal to market as a hdtv). I know from previous experience with my galaxy s4, which the samsung video app would mirror only the video at the correct tv resolution, leaving the phone as the remote. You could also use other apps while any video was playing through the samsung watchon (video) app. So randomly downloaded the vlc beta off the play store. It works for the tegra note 7 the same way samsung set up theirs, minus the multitasking(so far). It took me weeks on and off being frustrated with apps that wouldn't recognise that mirroring was enabled to take advantage of the external display. It's kinda whatever now seeing how much time I spent trying to get the video to play properly by itself, for my s4 I tried mhl cables, chromecast, dlna. this works a lot better
So if you just want videos to play, use the vlc player beta. you can use miracast or hdmi. works the same with both. Only if I could miracast surround sound. that would be nice.
I've just started using my tablet and a HDMI cable to run XBMC. This tip has saved me much frustration.
I already use Tasker which can send terminal commands as an action to make it easier. Tasker does have a HDMI plugged state which should allow this to be automated but for some reason tasker doesn't seem to detect it, not sure why yet.
So I've been fiddling a bit more to optimiser the HDMI experience. I've discovered an app called second screen that let's you sert display profiles and launch then the HDMI is plugged in. Thee app sets the size, resolution, dims the screen and force closes the UI to make sure the new settings actually come into effect. It will also revert the changes when the cable is removed. Does need to run on a rooted device but mine is already.

[Q] YCbCr support

Seems like nexus player supports only RGB limited. Since my HDMI port (which is shared by other sources) is configured for full RGB this results in poor blacks when I switch to nexus player. Anybody knows if it can be switched by to full RGB or even better to YCbCr? Since its a dedicated player I am thinking this should be a must. Even chromecast behaves better in that department.
Are you me? I've had the same issue, and asked on the Nexus help forum about it. "Paul from Google" says that there's no way to get RGB Full.
I'm pretty sure it could be done with a custom kernel though.
http://referencehometheater.com/2014/commentary/rgb-full-vs-limited/ - here is some explanation. I have my TV set on Auto and have never noticed any problems. Will have to check if it is able to display <16 black and white above 235 - by the way limited RGB is almost as stupid as overscan in TVs. What were they thinking limiting the colors like that?
Exactly !!! If a company expects to win the home theater section of any house and gain respect with the videophiles these details are elementary. Even if for whatever reason they decide to keep this behavior as a default, just add a video section in settings where the user can configure the way he/she wants.
Did a test with a black clipping pattern and the Chromecast is able to show 1-16 but the Nexus Player does not unfortunately.
If a TV's brightness is calibrated so that 16 is reference black though, does it matter I wonder that the Nexus Player can't show 1-16 with the assumption that Shows and Movies from the Google Play store are all 16-235 anyways (is that a correct assumption)?
looking over the kernel code it seems that the hardware will support these color ranges, lots of code to dig through, right now im looking through:
https://github.com/ion-storm/nexusplayer/tree/dev/drivers/external_drivers/intel_media which contains the hdmi video drivers, right now I cant seem to find where I can enable the option, lots of code to look though.
I believe that google support guy meant that there is no ui toggle to switch between these ranges, but what we can do is force detection/color ranges within the kernel if the hardware supports it, this is new code here so if anyone can find any references on enabling this, I'll be happy to look it over.

Mate 9 Pro daydream VR experiences

With firmware version b182 (eg: LON-L29C636B182) finally supporting Daydream VR correctly (B181 was broken), and with B182 downloadable via firmware finder, i thought it would make sense to discuss actual daydream VR experiences on Mate 9 pro.
I only have it running since a few hours, so not been able to try out various applications. I am using daydream VR viewer with the mate 9 pro.
My first quick observations:
head tracking is perfect.
The daydream VR controller seems to be quite versatile, but using the apps via it probably will take me a lot more time.
video quality: there is a very visible lattice structure in the video from the pixels. When moving the head it also seems very clear that the picture update is interlaced (aka: moving head around shows typical interlacing structures). This makes the picture very smeared when moving the "somehat faster". I would guess that the refresh rate is 60, so 60 frames interlaces ? There is also some smearing when moving the head up & down. Not quite sure yet what the reason for that could be.
I can not compare to other VR devices because i do not have them. Wonder if 60i is state of the art in cellphones.
So, i'd be happy to pay for a 4K phone with 60p refresh
Mine is still waiting for Huawei to authenticate the update. If you have set up HiCare account, would you mind sharing which Region you chose? I heard from somewhere that different regions in HiCare may speed up the authentication process and wanna try it.
Lets continue the discussions about the problems of getting firmware upgrades out of this thread, but lets use the existing thread instead: https://forum.xda-developers.com/mate-9/help/mate-9-pro-daydream-t3583311
i'd like to know which region your hicare is set up too. even if that's not the real reason why some people are able to authenticate the update even without a hicare account.
I wonder if anyone has tried Daydream on the regular Mate 9? The feedback on that screen is that it produces blurs and trails? I was wondering if someone took the unofficial way and installed Daydream on there, before I commit to purchasing a Dadydream helmet.

Categories

Resources