Related
]Okay, now I understand this phone simply have this problem where the camera constantly tries to refocus during video recording and it affect all OnePlus, this is my third OnePlus.
For some reason the Cyanogen Rom and roms based on it lack some drivers that allows continuous autofocusing to work correctly while video recording. Depends on what camera apps you use, the autofocusing will either not work, or it will continuously tries to re-focus nonstop. ColorOS however does have this function working correctly.
Solution: Use ColorOS + CameraNext or Google Camera.
If it matters that much to you then find the bug report on Jira and up vote it, that's the only real effective way to have an impact. You're not likely to find a fix at the ROM level.
Transmitted via Bacon
See post 1.
eksasol said:
]Okay, now I understand this phone simply have this problem where the camera constantly tries to refocus during video recording and it affect all OnePlus, this is my third OnePlus.
For some reason the Cyanogen Rom and roms based on it lack some drivers that allows continuous autofocusing to work correctly while video recording. Depends on what camera apps you use, the autofocusing will either not work, or it will continuously tries to re-focus nonstop. ColorOS however does have this function working correctly.
Solution: Use ColorOS + CameraNext or Google Camera.
Click to expand...
Click to collapse
Thanks for posting a solution. This problem is driving me crazy enough to sell my phone since I often need to use it to take short videos at work, and it is so embarrassing to have to show the videos to others that I have taken to also carrying around a small point-and-shoot, and this is not acceptable. I have tried many roms and many camera apps, but all of them have the video refocus issue.
However, I don't see Color OS in XDA. Is there a rom thread for it? I will try anything to salvage this phone since I love it except for this problem.
phoneturf said:
Thanks for posting a solution. This problem is driving me crazy enough to sell my phone since I often need to use it to take short videos at work, and it is so embarrassing to have to show the videos to others that I have taken to also carrying around a small point-and-shoot, and this is not acceptable. I have tried many roms and many camera apps, but all of them have the video refocus issue.
However, I don't see Color OS in XDA. Is there a rom thread for it? I will try anything to salvage this phone since I love it except for this problem.
Click to expand...
Click to collapse
You'll find several builds of ColorOS in our General section.
Transmitted via Bacon
This also appears to be a fix
I flashed the v20 mod for the app at http://forum.xda-developers.com/oneplus-one/themes-apps/app-cameranext-modded-t2999275 and it does not continually autofocus. I saw no need to flash the "click fix" since it is does not click when using it. I am on KK Slim.
phoneturf said:
Thanks for posting a solution. This problem is driving me crazy enough to sell my phone since I often need to use it to take short videos at work, and it is so embarrassing to have to show the videos to others that I have taken to also carrying around a small point-and-shoot, and this is not acceptable. I have tried many roms and many camera apps, but all of them have the video refocus issue.
However, I don't see Color OS in XDA. Is there a rom thread for it? I will try anything to salvage this phone since I love it except for this problem.
Click to expand...
Click to collapse
The official ColorOS firmware for some reason I could not get to boot on my phone, but you have to use the official version if you want working OTA updates. And it lack Gapps so you have to manually install it.
You could use other custom version like this one which is what I'm using, it's flashable using TWRP. http://forum.xda-developers.com/oneplus-one/general/rom-4-4-2-coloros-2-0-36beta-t2955853
The official OppoCamera.apk still do not record with continuous focusing, but the CameraNext.apk and Google Camera does.
Now that the Android P preview is out and we developers start seeing the consequences of the upcoming hidden API remove, i wonder if everyone is fully aware of the profound paradigm shift this will be!?
Going through my app Automate, i can say it will be painful. A lot of common Android features, excepted by users for years, will likely cease to function, or have to be reverted back to buggy behavior.
I expect and accept (my app users will not) that features requiring a rooted device will no longer be accessible, like toggling tethering, NFC, mobile data, etc.
But a lot of harmless hacks will also stop working, and the Play Store is full of innovative apps using them, like audio routing, BT utilities, whatever.
The more dire consequence is for working around current and future bugs. My app is has implemented a lot of workarounds relying on reflection for Android versions going back to 4.0. Even Google does this, like the PRNGFixes a few years ago.
In the future such workarounds may not be possible! Expecting Google to start fixing bugs is a pipe dream. I've report ~30 issues myself, starred 300+, and the majority of them are ignored, or has been flagged "Assigned" for years, "WontFix" or "Obsolete".
The proper solution for preventing use of the hidden APIs are to protect the "dangerous" ones with permissions, not blocking us from accessing them altogether.
We developers are battling Android fragmentation with every new release, often using reflection, so claiming to do this for "Improving Stability" is an insult.
I was hoping XDA developers, and others with influence, could get Google to listen, like with the Accessibility API usage ban.
I don't think a single article, which seems to overlook the serious consequence, will suffice.
Developers need to revolt, or if you've already conseede, at least report your hidden API usage here.
PS. Please, anyone with a rooted Android P, could you help me with some tests?
ballzak said:
I expect and accept (my app users will not) that features requiring a rooted device will no longer be accessible, like toggling tethering, NFC, mobile data, etc.
Click to expand...
Click to collapse
Not sure this part is true. According to Quinny899:
"I've just noticed when poking around in P that the warning toast for reflection doesn't fire when the code is run as root
They're not blocking root
That's why my apps still work then"
Let me see what joaomgcd has to say. He's still going through the P release IIRC.
MishaalRahman said:
Not sure this part is true. According to Quinny899:
"I've just noticed when poking around in P that the warning toast for reflection doesn't fire when the code is run as root
They're not blocking root
That's why my apps still work then"
Let me see what joaomgcd has to say. He's still going through the P release IIRC.
Click to expand...
Click to collapse
I'm only seeing the warning dialog in debug builds.
Everything still works in my app as well, since Google doesn't enforce the blacklisting yet.
Them excluding root processes gives some encouragement, but the most serious consequence remain.
ballzak said:
I'm only seeing the warning dialog in debug builds.
Everything still works in my app as well, since Google doesn't enforce the blacklisting yet.
Them excluding root processes gives some encouragement, but the most serious consequence remain.
Click to expand...
Click to collapse
Yes, I agree with you that this is a serious change. Our very own One-Handed Mode app will cease functioning in the final P release. There's nothing we can really do about that.
MishaalRahman said:
Yes, I agree with you that this is a serious change. Our very own One-Handed Mode app will cease functioning in the final P release. There's nothing we can really do about that.
Click to expand...
Click to collapse
That's sad. As i said, there's lots of innovative apps that will be affected.
Hence my wonderment for lack of outrage, we must make Google listen!
ballzak said:
That's sad. As i said, there's lots of innovative apps that will be affected.
Hence my wonderment for lack of outrage, we must make Google listen!
Click to expand...
Click to collapse
The problem is that we need developers to be outspoken about what will be broken in their apps because of these changes. If developers are upfront about what will happen, it will encourage users to get involved too. Right now, I only have my own example to share. And you are sharing your example. What are apps will be affected, and how will they be affected? Knowing that is key for getting support on this issue.
MishaalRahman said:
The problem is that we need developers to be outspoken about what will be broken in their apps because of these changes. If developers are upfront about what will happen, it will encourage users to get involved too.
Click to expand...
Click to collapse
Let's hope so, that's why i posted.
I fear developers are underestimating the consequences, once Android P goes live, and the blacklist kicks in, it's too late!
Hi there.
I too have this issue regarding some of my app's functionalities. What I'm doing is reporting any hidden API I use here. They seem to respond pretty quickly, at least they did with my last submission.
Did you try that? Thanks!
joaomgcd said:
Hi there.
I too have this issue regarding some of my app's functionalities. What I'm doing is reporting any hidden API I use here. They seem to respond pretty quickly, at least they did with my last submission.
Did you try that? Thanks!
Click to expand...
Click to collapse
I've reported 9 requests thus far, no response.
ballzak said:
I've reported 9 requests thus far, no response.
Click to expand...
Click to collapse
Interesting. I've reported 2 (one just today) but for the first one I got a response right away. I'm still figuring out how it'll affect my apps exactly.
joaomgcd said:
Interesting. I've reported 2 (one just today) but for the first one I got a response right away. I'm still figuring out how it'll affect my apps exactly.
Click to expand...
Click to collapse
Are you reporting "light graylist", "dark graylist", or both?
I'm currently only reporting the "light graylist" cases, since Google already decided to block the "dark graylist".
What Priority are you reports flagged as, P2 or P3?
I got to contact Google through some other channel if they're ignoring/binning my requests.
ballzak said:
Are you reporting "light gray", "dark gray", or both?
I'm currently only reporting the "light gray" cases, since Google already decided to block the "dark gray".
What Priority are you reports flagged as, P2 or P3?
I got to contact Google through some other channel if they're ignoring/binning my requests.
Click to expand...
Click to collapse
I reported one that isn't in those "gray" lists: RCS support. It's assigned a P3 priority.
I added another one (Bluetooth Tethering) which is light gray and is assigned a P3 priority as well.
joaomgcd said:
I reported one that isn't in those "gray" lists: RCS support. It's assigned a P3 priority.
I added another one (Bluetooth Tethering) which is light gray and is assigned a P3 priority as well.
Click to expand...
Click to collapse
Just added another request, for a bug workaround, all assigned P3.
Probably wont get a response on this one either. :crying:
Let us know if they ever respond and I'll do the same.
They've responded to another one of my requests now!
joaomgcd said:
They've responded to another one of my requests now!
Click to expand...
Click to collapse
Yey, 3 of 10 requests got a response now.
Seems like the intern on bug tracker duty has awaken. :fingers-crossed:
Did any of the bugs change to a "planned" status or something similar?
joaomgcd said:
Did any of the bugs change to a "planned" status or something similar?
Click to expand...
Click to collapse
No, two lesser issue seems to have been added to a "hotlist".
Enable "Full history" in the upper right corner on an issue page.
Check out a reply to one of my bugs
For future planning, I think we may want to consider some 'device automation' permission bucket.
Click to expand...
Click to collapse
All my reported APIs are now "assigned". Seems like good progress.
Hey everyone
Very glad to announce that the Android Pie 9.0 Update is now rolling out to Razer Phone 1 devices right now!
I personally want to thank you all for being so patient, I know this was a long time coming but thank you for holding on and sticking with the team.
Now go get your pie update!
PSA: Game Booster is broken.
I'll get this passed on asap but for now just reset game booster
(System settings>game booster> tap the reset icon on the top right hand corner) and don't change any settings for now.
EDIT 2: The update has been temporarily pulled due to the Game Booster issue.
I'll let you all know when the rollout starts again.
EDIT 3: Update is live again folks! However there's an issue with the do not disturb function if you have it on its making the camera force close.
It's been reported and hopefully we'll see a fix soon.
When I try launch game there is black screen, I can hear the sounds and play but the screen is black....
I just received the update as well in US
I just got the update. not happy at all. Don't like the new UI but even worse games don't work. Black screen and also the camera app crashes every time i try to open it. Doing a factory reset hasn't helped either.
raynor1985 said:
I just got the update. not happy at all. Don't like the new UI but even worse games don't work. Black screen and also the camera app crashes every time i try to open it. Doing a factory reset hasn't helped either.
Click to expand...
Click to collapse
Mine updated first thing this morning. Dont mind the new UI and not had issues with the camera (Google Apk or the Razer camera) but like you no games.
I did as some mentioned above and reset Game Booster and didnt touch the settings on it also put Cortex on as well. All my games work now but theyre all set to what ever Booster defaults are.
The only other thing ive noticed is i now get 4G+ which i didnt before.
download link?
Flashed stock just for the download and no update. wasted my time. flashed LOS 16 again.
Can't open camera after upgrading to 9.0 .
has to use facebook messenger to take photos !
Google Chrome crash all the time !
damn stupid phone.
leepc said:
Can't open camera after upgrading to 9.0 .
has to use facebook messenger to take photos !
Google Chrome crash all the time !
damn stupid phone.
Click to expand...
Click to collapse
Everything was working apart from games when i first did the update. Thought something might have messed up so i did a master reset on my phone. Everything still works even games with the booster reset tweak. Put the google camera apk on as well as better options than the stock Razer camere app and thats fine too.
(Update - just resetting Booster worked for a while then the games stopped displaying again so ive disabled Booster now and everything is working as it should be)
Don't suppose anyone has the update backed up for us poor people who missed it
This
Nothing to announce just yet I'm afraid everyone.
Soon as I know something I'll let you all know on the usual channels.
Update available
cobben said:
Update available
Click to expand...
Click to collapse
Most things seem to work, do not have a simcard in it to test with.
Only problem so far:
Razer Camera app & Gcam FC.
Open Camera works with back lens, FC when switching to front lens.
Clearing app data does not help.
Reinstalling Gcam does not help.
Razer Camera cannot be uninstalled.
??
Edit:
Left it alone for awhile, and all the camera apps started working.
??
Should have updated the security patch to September 2019
Can someone capture the ota link or zip please?
I updated before they pulled it and no new update now. Game booster still black screens games.
Anyone installed new firmware and game booster working?
Here's the OTA link: https://android.googleapis.com/pack.../3d911fb507d6efdf1cf66552a5f15a3a8f465dba.zip
anyone can boot twrp with the new update? I need to extract the boot.img for magisk and it's not working for me D:
I hope some enlightened dev can pull the useful bits from this update (if it is working) and use that to fix the quirks on phh's Pie treble build. I never got the camera working with it (I can live with the BT bug)
guillermohs9 said:
I hope some enlightened dev can pull the useful bits from this update (if it is working) and use that to fix the quirks on phh's Pie treble build. I never got the camera working with it (I can live with the BT bug)
Click to expand...
Click to collapse
this build of camera work fine for me MGC_6.1.021_RP1_V1.3.2-BSG. it is in the forum (don't know the exact address). The only con I have with the pie is that the battery drains fast (6% in 8 hours standby) or it might be my phone which needs a battery change.
---------- Post added at 10:47 PM ---------- Previous post was at 10:41 PM ----------
Kantana said:
I updated before they pulled it and no new update now. Game booster still black screens games.
Anyone installed new firmware and game booster working?
Click to expand...
Click to collapse
game booster working on mine with new update.
Autofill seems to have been broken on my Xiaomi Poco X3 running MIUI Android 11.
On a webpage with a text entry box (search for items on site, etc). I get the usual drop-down list of previous search terms. Up to a few days ago, I was able to touch on a previous search term and have it used.
For the last few days I get the usual dropdown list but can't actually select anything!
It certainly happens on Brave browser and on Chrome.
I can still paste from the Gboard clipboard and use suggestions from Gboard.
So far I have cleared cache and forced stop on both Brave and Chrome browsers. I have rebooted. I have reinstalled Brave browser. I have uninstalled updates on GBoard and reinstalled.
Autofill remains broken.
There seems to be quite a few people asking the same question. See https://forums.androidcentral.com/ask-question/1034943-how-fix-autofill-not-working.html#post7009398
Does anyone here have /know of similar issues? Has Xiaomi pushed out a faulty update?
Same happening with me also in Poco X3
Well, I've had a winge at Xiaomi support. If loads of other folk do as well, something MIGHT be done.
developerpritam said:
Same happening with me also in Poco X3
Click to expand...
Click to collapse
I have been getting positive responses (so far at least) from
https://mobile.twitter.com/XiaomiSupport
It may be worth trying there.
The problem is with update 12.5.4.0 (Poco X3 NFC Global).
I was lucky enough to have two Poco X3 NFC (mine and my wife). She started complaining about this autofill problem. My phone was working fine. After comparing settings, I noticed her phone had updated to 12.5.4.0. Mine was still on 12.5.3 or whatever the previous official release was. I proceeded to update my phone to 12.5.4.0 like hers and sure enough, my autofill also stopped working. So the bug was introduced with that update.
Lukus2021 said:
The problem is with update 12.5.4.0 (Poco X3 NFC Global).
I was lucky enough to have two Poco X3 NFC (mine and my wife). She started complaining about this autofill problem. My phone was working fine. After comparing settings, I noticed her phone had updated to 12.5.4.0. Mine was still on 12.5.3 or whatever the previous official release was. I proceeded to update my phone to 12.5.4.0 like hers and sure enough, my autofill also stopped working. So the bug was introduced with that update.
Click to expand...
Click to collapse
Thanks for that observation. My wife too has the same phone as me (both bought at the same time). Here is on 12.5.4.0 and doesn't exhibit this problem! I use Brave browser (Chrome derived) and Chrome itself. Hers just uses Chrome. Dunno if that is relevant.
What browser(s) are you using?
Lukus2021 said:
The problem is with update 12.5.4.0 (Poco X3 NFC Global).
I was lucky enough to have two Poco X3 NFC (mine and my wife). She started complaining about this autofill problem. My phone was working fine. After comparing settings, I noticed her phone had updated to 12.5.4.0. Mine was still on 12.5.3 or whatever the previous official release was. I proceeded to update my phone to 12.5.4.0 like hers and sure enough, my autofill also stopped working. So the bug was introduced with that update.
Click to expand...
Click to collapse
As above, you might like to talk to Xiaomi on Twitter (https://mobile.twitter.com/XiaomiSupport)
The more people piling in the better.
Allthecoolnamesweretaken said:
Thanks for that observation. My wife too has the same phone as me (both bought at the same time). Here is on 12.5.4.0 and doesn't exhibit this problem! I use Brave browser (Chrome derived) and Chrome itself. Hers just uses Chrome. Dunno if that is relevant.
What browser(s) are you using?
Click to expand...
Click to collapse
That's strange. I still think the issue surfaced with the latest update but something differs between your phone and hers but who knows if it's a settting or what. I did try different browsers and the problem remains.
Lukus2021 said:
That's strange. I still think the issue surfaced with the latest update but something differs between your phone and hers but who knows if it's a settting or what. I did try different browsers and the problem remains.
Click to expand...
Click to collapse
Weird, isn't it? Have a go at Xiaomi support on Twitter. The more the merrier.
Allthecoolnamesweretaken said:
As above, you might like to talk to Xiaomi on Twitter (https://mobile.twitter.com/XiaomiSupport)
The more people piling in the better.
Click to expand...
Click to collapse
I did chat with them. They had me download the latest package which I did and installed. It did not resolve the autofill issue. Waiting for them to suggest something else.
Lukus2021 said:
I did chat with them. They had me download the latest package which I did and installed. It did not resolve the autofill issue. Waiting for them to suggest something else.
Click to expand...
Click to collapse
OK. Thanks for letting me know. They had me do the same, with the same result.
I'll post again when/if I hear anything more.
Cheers and good luck
Definitely the update. Went into Chrome app info (long press icon) and there was an option to uninstall update.
Since I did that auto fill now functions correctly
Well, it seems latest versions of Chrome and Brave browser (Chrome based anyway) don't play nice with MIUI 12.5.4.
YMMV but this worked for me. I just uninstalled the Chrome updates and that restored Autofill there. I then found an earlier version of Brave on apkmirror, installed that and we have autofill there too.
Yep. Latest Chrome update is the culprit. Just not sure if it got updated with the package as mine stopped working right after that update. Nevertheless, uninstalling the latest Chrome update restored the autofill function.
Well, Chrome and the Chrome derived browser Brave have been updated and it's good to report after a short while using Brave, that autofill now works.
Now, about all those mindless ads that get pushed by Xiaomi phones. When are they going to stop annoying people with them?
Examples below
My widevine is L1 I have tried reboots ,changing colors from vivid to natural or cinematic etc.
I have tried factory resets.
I have tried custom roms.
Ever since a11 to a12 and a13 the problem persists.Im out of options
Edit: YouTube HDR on the other hand looks stunning....no issues at all nor prime or Disney plus, (I also tried changing quality and downlaoding) , if you take as example episodes that are very dark like warrior nun season 2 ep 4 the problem is in every scene and in 15:35 whilst the girls head is out of focus it becomes oily like in the above pictures. The only part that isn't oily I'd a part of the "angels" face
This is caused by a low color depth - the "resolution" of the color spectrum used by the encoding algorithm. Try adjusting your quality settings for something higher. Lower bitrates use a lower color resolution to save data at the expense of quality.
Menu > Account > Profile & Parental Controls > select profile > Playback Settings > select Medium or High
V0latyle said:
This is caused by a low color depth - the "resolution" of the color spectrum used by the encoding algorithm. Try adjusting your quality settings for something higher. Lower bitrates use a lower color resolution to save data at the expense of quality.
Menu > Account > Profile & Parental Controls > select profile > Playback Settings > select Medium or High
Click to expand...
Click to collapse
Right.
Apologies.
I wasn't clear enough .
I tried everything sort of buying a new phone (as far as I know)
Thank you very much for replying to me but I have tried that before (other ideas would be welcome of course).
Whether it's streaming or doelaoding whether it's auto or low or high or standard.
The problem will persist.
The exception are cartoons for now like archer....haven't seen a problem but I don't think they have HDR for a cartoon (I don't even know if that's possible)
nickpatellis said:
Right.
Apologies.
I wasn't clear enough .
I tried everything sort of buying a new phone (as far as I know)
Thank you very much for replying to me but I have tried that before (other ideas would be welcome of course).
Whether it's streaming or doelaoding whether it's auto or low or high or standard.
The problem will persist.
The exception are cartoons for now like archer....haven't seen a problem but I don't think they have HDR for a cartoon (I don't even know if that's possible)
Click to expand...
Click to collapse
Sign into your Netflix account on a computer and see if the same thing happens.
I suspect it might be something to do with their HDR encoding. It's not a problem with your device.
V0latyle said:
Sign into your Netflix account on a computer and see if the same thing happens.
I suspect it might be something to do with their HDR encoding. It's not a problem with your device.
Click to expand...
Click to collapse
Actually it only happens on my device....I use 3 more phones one tv and on laptop and on ps4....
I don't see the problem in any of them
nickpatellis said:
Actually it only happens on my device....I use 3 more phones one tv and on laptop and on ps4....
I don't see the problem in any of them
Click to expand...
Click to collapse
Considering that YouTube works properly it still doesn't sound like it is a device issue, but rather how the Netflix app is displaying things. Open a ticket with Netflix to see if they have a suggestion.
V0latyle said:
Considering that YouTube works properly it still doesn't sound like it is a device issue, but rather how the Netflix app is displaying things. Open a ticket with Netflix to see if they have a suggestion.
Click to expand...
Click to collapse
So update.
I used msm to roll back to Android 11.
That fixed it.
Although I suspect that even though I was l1 the HDR didn't kick in...very weird...
After I updated to a12 the problem came back again
nickpatellis said:
So update.
I used msm to roll back to Android 11.
That fixed it.
Although I suspect that even though I was l1 the HDR didn't kick in...very weird...
After I updated to a12 the problem came back again
Click to expand...
Click to collapse
Odd. Since it doesn't happen with YouTube I think it has something to do with how the Netflix app works with Android 12 on your device. For example, maybe it's the graphics/display API in Android 12, or maybe it's DRM requirements.
I wonder if it has something to do with integrity/security attestation as Netflix requires DRM. If you're willing to do more testing, roll back to Android 11, and use this app to check your Play Integrity attestation. Do the same thing for Android 12. I assume your bootloader is unlocked? Are you using Magisk?
V0latyle said:
Odd. Since it doesn't happen with YouTube I think it has something to do with how the Netflix app works with Android 12 on your device. For example, maybe it's the graphics/display API in Android 12, or maybe it's DRM requirements.
I wonder if it has something to do with integrity/security attestation as Netflix requires DRM. If you're willing to do more testing, roll back to Android 11, and use this app to check your Play Integrity attestation. Do the same thing for Android 12. I assume your bootloader is unlocked? Are you using Magisk?
Click to expand...
Click to collapse
I rolled back to a11 yesterday.
I didn't use your app cause I hadn't seen the message...I must have done so around 3 times.... Every single time my Netflix issues were replaced by a green tint all over the screen no matter the brightness.
I am using magisk in fact now I am using Android 13 custom ROM evolution x.
The problem persists
V0latyle said:
Odd. Since it doesn't happen with YouTube I think it has something to do with how the Netflix app works with Android 12 on your device. For example, maybe it's the graphics/display API in Android 12, or maybe it's DRM requirements.
I wonder if it has something to do with integrity/security attestation as Netflix requires DRM. If you're willing to do more testing, roll back to Android 11, and use this app to check your Play Integrity attestation. Do the same thing for Android 12. I assume your bootloader is unlocked? Are you using Magisk?
Click to expand...
Click to collapse
Welp.
Nevermind.
I have the same problem with YouTube now...
Ex.
(I would think display issues wouldn't appear on a Screenshot right?
Most of those look fine, although I do see some blotching in the background of this one...
V0latyle said:
Most of those look fine, although I do see some blotching in the background of this one...View attachment 5780389
Click to expand...
Click to collapse
You really don't see that?
Anyway whatever you see here on Netflix its 10 times worse.
And I'm not exaggerating
nickpatellis said:
You really don't see that?
Anyway whatever you see here on Netflix its 10 times worse.
And I'm not exaggerating
Click to expand...
Click to collapse
Yeah, I see it. It only seems to be in the background though, I think that's normal because it helps keep the bit rate down. Notice how the foreground subject (facial features) don't show the same blotching. I have noticed this with not only streaming services but with most 720p video. I don't know if there is any way to fix it, sorry.
V0latyle said:
I believe you, I just don't know why it's happening or how to fix it. Sorry.
Click to expand...
Click to collapse
That's alright man.
Appreciate you replying to me
V0latyle said:
Yeah, I see it. It only seems to be in the background though, I think that's normal because it helps keep the bit rate down. Notice how the foreground subject (facial features) don't show the same blotching. I have noticed this with not only streaming services but with most 720p video. I don't know if there is any way to fix it, sorry.
Click to expand...
Click to collapse
Actually in Netflix faces have the same issue as the one above only it's almost the whole face sometimes (I believe I sent a photo of a face originally)