Related
Taken from:
http://developer.android.com/sdk/android-2.3-highlights.html
Support for new media formats
The platform now offers built-in support for the VP8 open video compression format and the WebM open container format. The platform also adds support for AAC encoding and AMR wideband encoding (in software), so that applications can capture higher quality audio than narrowband.
Click to expand...
Click to collapse
Implementing wideband codecs in video capture would be very nice as the platform now allows it, because at the moment, captured audio in videos is simply very, very bad (8kHz narrowband AMR).
Any dev willing to explain how hard would it be to implement this? Thanks.
Galaid said:
Taken from:
http://developer.android.com/sdk/android-2.3-highlights.html
Implementing wideband codecs in video capture would be very nice as the platform now allows it, because at the moment, captured audio in videos is simply very, very bad (8kHz narrowband AMR).
Any dev willing to explain how hard would it be to implement this? Thanks.
Click to expand...
Click to collapse
Can be done, but first we'll need to fix the video encoder framework problem currently found in gingerbread.
With the OTA ull have both AAC and amrwb encoding, no need to worry about that, just wait for the ota. i have seen the AOSP source for passion, there is implementation of all the new encoders
charnsingh_online said:
..just wait for the ota..
Click to expand...
Click to collapse
Isn't the libs part of AOSP?
No passion has some proprietary libs including camera n omx libs. We also need a new radio to go along with the encoders
charnsingh_online said:
No passion has some proprietary libs including camera n omx libs. We also need a new radio to go along with the encoders
Click to expand...
Click to collapse
One and half month after SDK and waiting...
Well, the OTA is here and the camera still encodes audio in AMR.
Damn.
edit: well, I was wrong! I hadn't looked at the actual file with a computer: it now has AAC audio, 16k sampling rate, 96kbps mono. It also uses the back mic (i don't know if that was the case before)
A higher sample rate would be very nice, but ah well, at least it's something
spamlucal said:
Well, the OTA is here and the camera still encodes audio in AMR.
Damn.
edit: well, I was wrong! I hadn't looked at the actual file with a computer: it now has AAC audio, 16k sampling rate, 96kbps mono. It also uses the back mic (i don't know if that was the case before)
A higher sample rate would be very nice, but ah well, at least it's something
Click to expand...
Click to collapse
Thanks for revivng the thread, I had problems finding it. So as aac is in the game now, is the sound better or just cosmetically better?
spamlucal said:
Well, the OTA is here and the camera still encodes audio in AMR.
Damn.
edit: well, I was wrong! I hadn't looked at the actual file with a computer: it now has AAC audio, 16k sampling rate, 96kbps mono. It also uses the back mic (i don't know if that was the case before)
A higher sample rate would be very nice, but ah well, at least it's something
Click to expand...
Click to collapse
How do you know its using the back Mic?
Alright, as promised, the camera patch for all ROMs using the grouper blobs.
First of all, a very big thanks to @Adam77Root, cause without him, none of this would have been possible.
This patch allows the camera to use the old nvomx, which fixes the encoder issues. However, this breaks the hardware decoder of the stock gallery. And using software decoder, lags are inevitable. But, you can still play HD videos using MX player.
To revert this, either restore a system backup, re-flash your ROM or flash the "Cam_revert_patch.zip" from the Attachment.
@ROM devs, please don't include this patch into your ROMs, but rather link to this thread. Not being able to use the read hw decoder can cause confusion and false bug reports, which is why I want people to read this first, before using the patch
Good idea!
tested the patch, works wonderfully. thank you!
As above working flawlessly as it should good work you are one step to make everything fully working
Sent from my LG-P880 using Tapatalk
Can anyone test Skype videocall? Because for me it doesn't work, it gives me the same error as without the patch (green screen instead of the video). I can record videos though.
Also it works with the new omni buils (the ones reverted to old blobs) and all other official roms that use old blobs.
qr decoding/skype still doesn't work - this is just a fix for video recording
I would really like a revert patch, because I would like to install the patch when I want to take a video and simply uninstall it when I want to use the gallery.
I also add that this patch breaks Youtube app
Nagass said:
I also add that this patch breaks Youtube app
Click to expand...
Click to collapse
Confirmed, output when playing a video is only black screen
breaks also flashplayer...
Nagass said:
I also add that this patch breaks Youtube app
Click to expand...
Click to collapse
JustChris20 said:
breaks also flashplayer...
Click to expand...
Click to collapse
Of course, it breaks almost all video decoding stuff, especially YT. This is why don't want devs to include it into ROMs.
MX player is more-less the only exception
in addition the recorded Videos are really "not good". The framerate is not stable. One video I recorded has 13 fps, the next 22 fps. Stable 25fps seems not possible.
So I would really appreciate a revert patch, dont want to flash all the rom again
Climuff said:
in addition the recorded Videos are really "not good". The framerate is not stable. One video I recorded has 13 fps, the next 22 fps. Stable 25fps seems not possible.
So I would really appreciate a revert patch, dont want to flash all the rom again
Click to expand...
Click to collapse
you were watching this videos on gallery app ?? or mx player with s/w decoding chosen? or on your pc?
i didnt faced such problem.. only when u watch video you recorded on gallery it OFC will lag...
I watched the videos on my pc, I read the framerate out with standard windows and also with adobe premiere pro cs5.
Climuff said:
I watched the videos on my pc, I read the framerate out with standard windows and also with adobe premiere pro cs5.
Click to expand...
Click to collapse
What's your recorded resolution?
About the revert patch, I'm on it
I recorded in 1080p H.264 with LED on and USB connected. Video was saved on internal storage.
Climuff said:
I recorded in 1080p H.264 with LED on and USB connected. Video was saved on internal storage.
Click to expand...
Click to collapse
What's the bitrate of the recorded vid?
BTW, revert patch added to the OP
laufersteppenwolf said:
What's the bitrate of the recorded vid?
Click to expand...
Click to collapse
this one which ended up with 13 fps is 11.5 mbits and this one which has 22 fps is 10.3 mbits.
Climuff said:
this one which ended up with 13 fps is 11.5 mbits and this one which has 22 fps is 10.3 mbits.
Click to expand...
Click to collapse
Will do some troubleshooting tomorrow, gonna let you know if I find anything
Alright, as already mentioned HERE, we have a new way to switch between video playing and recording, a more "on the go" version
For details and how to use it, please take a look into the linked post
Now, some more explanation, the new patch "nameless_patchV2" is not only for nameless, but all ROMs built using p880-dev's android-4.4 branch, such as NamelessROM, Omni, Thinkingbridge, ...
Just flash the patch and you can switch blobs as explained.
The patch for CM11 (the cm-11.0 branch) is in the making
I`ve installed CWM 12.1 on my s advance ...................... as it was written in that thread that video recording will have green band, so is there any app or trick to use video camera in normal mode
It's hardware video encoding what's broken, so if an app use software video encoding it will work but at lower quality
enkflr said:
It's hardware video encoding what's broken, so if an app use software video encoding it will work but at lower quality
Click to expand...
Click to collapse
so what should i do to solve the problem, i have also heard that by using third party video recording app will solve the problem but which i have tried lots of app.
Patil.sid101 said:
so what should i do to solve the problem, i have also heard that by using third party video recording app will solve the problem but which i have tried lots of app.
Click to expand...
Click to collapse
I think this is often offered: VivaVideo: Free Video Editor or VivaVideo Pro:Video Editor App
Camu it's supposed to work too.
Those are the most common mentioned...
kilroy69 said:
I think this is often offered: VivaVideo: Free Video Editor or VivaVideo Pro:Video Editor App
Click to expand...
Click to collapse
Thanks ..... it works
asd_sh .
posted this
cm12.1 fix Camera - Video recording
: flash this
www.goo.gl/lUkVot
you can try for yourself, but it litreally slowed down my camera , but yea video is recording . ,it replaced stock camera of my rom
I've read that it's not a real fix, it just replace the stock camera with camu...
I haven't tried, that's just what I've read
It's more like a workaround than a fix
yep ! you are right
enkflr said:
I've read that it's not a real fix, it just replace the stock camera with camu...
I haven't tried, that's just what I've read
It's more like a workaround than a fix
Click to expand...
Click to collapse
but what to do now i tried it and now i got camu in my hone who doesn`t do anything and hangs alot, any way i can get stock cm12.1 cam back ?
eit : the fix is finaly here : http://forum.xda-developers.com/galaxy-s-advance/help/finally-fix-video-recording-bug-t33173
If I'm not wrong you can install cyanogen camera from playstore.
You can also flash a Gapps package that includes Google camera to get it as default I guess...
So this is our main problem.
Logcat says only: bufferitemconsumer: [stagefright-camerasource] failed to release buffer: unknown error -1
It's only related to google and aosp camera. every other cam working without this logcat message.
According to google we got this info:
http://forum.xda-developers.com/attachment.php?attachmentid=3887247&stc=1&d=1474924978
http://forum.xda-developers.com/attachment.php?attachmentid=3887250&stc=1&d=1474925299
Pass metadata in video buffers(HAL1 only). If HAL1 stores metadata instead of real YUV frame data in video buffers, the HAL must not store anything that is invalid across process boundaries, including native handles. If HAL passes native handles in the metadata in video buffers, you must update it to use kMetadataBufferTypeNativeHandleSource as the metadata buffer type and pass VideoNativeHandleMetadata in video buffers.
With VideoNativeHandleMetadata, camera and media frameworks are able to pass the video buffers between processes by serializing and deserializing the native handles properly. If HAL chooses to continue using kMetadataBufferTypeCameraSource as the metadata buffer type, the metadata must be able to be passed between processes as plain values.
Buffer handle address does not always store same buffer (HAL3 only). For each capture request, HAL3 gets addresses of buffer handles. HAL cannot use the addresses to identify buffers because the addresses may store another buffer handle after HAL returns the buffer. You must update the HAL to use buffer handles to identify the buffers. For example: HAL receives a buffer handle address A, which stores buffer handle A. After HAL returns buffer handle A, buffer handle address A may store buffer handle B next time the HAL receives it.
Click to expand...
Click to collapse
What do you think about this?
With media.stagefright.codecremote=false prop the glitch is gone and all working fine on aosp camera (but logcat message still persist). But in google camera still persist a green flickering on video record.
Edit:
So. Preview state is fine, Recording state is fine too. It seems the main problem will be stagefright/omx/encoder.
On marsmallow camera related stuff and codecs was in the same process/mediaserver/. Now on nougat camera service is out from mediaserver and it looks like in the code, all the codecs / video encoder and etc / are gone too to a separate codec process.
kamarush said:
So this is our main problem.
Logcat says only: bufferitemconsumer: [stagefright-camerasource] failed to release buffer: unknown error -1
It's only related to google and aosp camera. every other cam working without this logcat message.
According to google we got this info:
http://forum.xda-developers.com/attachment.php?attachmentid=3887247&stc=1&d=1474924978
http://forum.xda-developers.com/attachment.php?attachmentid=3887250&stc=1&d=1474925299
Pass metadata in video buffers(HAL1 only). If HAL1 stores metadata instead of real YUV frame data in video buffers, the HAL must not store anything that is invalid across process boundaries, including native handles. If HAL passes native handles in the metadata in video buffers, you must update it to use kMetadataBufferTypeNativeHandleSource as the metadata buffer type and pass VideoNativeHandleMetadata in video buffers.
With VideoNativeHandleMetadata, camera and media frameworks are able to pass the video buffers between processes by serializing and deserializing the native handles properly. If HAL chooses to continue using kMetadataBufferTypeCameraSource as the metadata buffer type, the metadata must be able to be passed between processes as plain values.
Buffer handle address does not always store same buffer (HAL3 only). For each capture request, HAL3 gets addresses of buffer handles. HAL cannot use the addresses to identify buffers because the addresses may store another buffer handle after HAL returns the buffer. You must update the HAL to use buffer handles to identify the buffers. For example: HAL receives a buffer handle address A, which stores buffer handle A. After HAL returns buffer handle A, buffer handle address A may store buffer handle B next time the HAL receives it.
What do you think about this?
With media.stagefright.codecremote=false prop the glitch is gone and all working fine on aosp camera (but logcat message still persist). But in google camera still persist a green flickering on video record.
Edit:
So. Preview state is fine, Recording state is fine too. It seems the main problem will be stagefright/omx/encoder.
On marsmallow camera related stuff and codecs was in the same process/mediaserver/. Now on nougat camera service is out from mediaserver and it looks like in the code, all the codecs / video encoder and etc / are gone too to a separate codec process.
Click to expand...
Click to collapse
Have you contacted any of the developers working on Nougat? Maybe they could adress this issue. It's kind of the only issue on our Rom's right now.
There is already some work ongoing around this in CM14.
See current merges: http://review.cyanogenmod.org/#/c/165009/ http://review.cyanogenmod.org/#/c/165008/ http://review.cyanogenmod.org/#/c/165140/
Video recording works with this, however, the camera crashes while saving the video with a "Can't connect to camera" error and the recorded video seems broken (meaning it's very sluggish and some frames seem duplicated).
It will eventually be fixed, as all devices pre-n use HAL1, we just need to be patient.
On the bright side, other applications seem to be working, so whoever needs video, can use those.
morphvale said:
There is already some work ongoing around this in CM14.
See current merges: http://review.cyanogenmod.org/#/c/165009/ http://review.cyanogenmod.org/#/c/165008/ http://review.cyanogenmod.org/#/c/165140/
Video recording works with this, however, the camera crashes while saving the video with a "Can't connect to camera" error and the recorded video seems broken (meaning it's very sluggish and some frames seem duplicated).
It will eventually be fixed, as all devices pre-n use HAL1, we just need to be patient.
On the bright side, other applications seem to be working, so whoever needs video, can use those.
Click to expand...
Click to collapse
Yes i know this.
But just for understand the problem. Google Camera now uses Camera API version 2 (at MM used Camera API version 1), so we need to update the HAL's buffer handle to be able to pass and release buffers between separate processes.
AOSP Camera and CM's Snap uses Camera API version 1, which is fine with our HAL with media.stagefright.codecremote=false prop. It's completely working.
So if @Santhosh M put the prop in the build, CM will be complete.
kamarush said:
Yes i know this.
But just for understand the problem. Google Camera now uses Camera API version 2 (at MM used Camera API version 1), so we need to update the HAL's buffer handle to be able to pass and release buffers between separate processes.
AOSP Camera and CM's Snap uses Camera API version 1, which is fine with our HAL with media.stagefright.codecremote=false prop. It's completely working.
So if @Santhosh M put the prop in the build, CM will be complete.
Click to expand...
Click to collapse
Will do the same
With some kernel related changes/patches now we can use all the camera apps without disabling the remote codecs. Except Google Camera....
Still don't know what causing that green flashes, but this is again one step forward.
@Santhosh M @yashade2001 @ganachoco @Mr.MEX
So guys i was completely wrong
With my last changes to dev-tree/QCamera2 and kernel Aosp Camera2 worked fine without disabling mediacodecs, but was still problem with Google Camera. So my fault was i always tried with GoogleCamera 3.X which was released with N dev preview. But the last N5 officially supported GoogleCamera is 2.7.008, and with that its working completely fine (HDR+ too) :good: No green flashes no glitches, so it's working fully. No need mediaserver and other hacks!
Feel free use it on your builds guys!
Cheers
kamarush said:
@Santhosh M @yashade2001 @ganachoco @Mr.MEX
So guys i was completely wrong
With my last changes to dev-tree/QCamera2 and kernel Aosp Camera2 worked fine without disabling mediacodecs, but was still problem with Google Camera. So my fault was i always tried with GoogleCamera 3.X which was released with N dev preview. But the last N5 officially supported GoogleCamera is 2.7.008, and with that its working completely fine (HDR+ too) :good: No green flashes no glitches, so it's working fully. No need mediaserver and other hacks!
Feel free use it on your builds guys!
Cheers
Click to expand...
Click to collapse
I knew 2.7 worked since long, just that i was figuring out for latest versions
kamarush said:
@Santhosh M @yashade2001 @ganachoco @Mr.MEX
So guys i was completely wrong
With my last changes to dev-tree/QCamera2 and kernel Aosp Camera2 worked fine without disabling mediacodecs, but was still problem with Google Camera. So my fault was i always tried with GoogleCamera 3.X which was released with N dev preview. But the last N5 officially supported GoogleCamera is 2.7.008, and with that its working completely fine (HDR+ too) :good: No green flashes no glitches, so it's working fully. No need mediaserver and other hacks!
Feel free use it on your builds guys!
Cheers
Click to expand...
Click to collapse
This is weird. In Android MM with custom roms like Dirty Unicorns or even in Stock MM provided by Google the Google Camera was working fine and let me to update it on Play Store. That brings a new UI where you can just swipe left and right to switch between photo and video mode.
I just tested the Google Camera that you provided (http://www.apkmirror.com/apk/google...-2130300-30-m-preview-3-android-apk-download/) and it works fine, but the UI is the old one.
Also you get the notification in the Play Store to update it, which brings the new UI and brokes video recording, so I think something is still wrong.
Sadly I can't install MM back to check what google camera version I had since I need to attend important stuff this days with phone. I'm getting a new phone someday next week(in like 1 to 3 days) and I will be able to gladly help you guys to test stuff.
Jaizu said:
This is weird. In Android MM with custom roms like Dirty Unicorns or even in Stock MM provided by Google the Google Camera was working fine and let me to update it on Play Store. That brings a new UI where you can just swipe left and right to switch between photo and video mode.
I just tested the Google Camera that you provided (http://www.apkmirror.com/apk/google...-2130300-30-m-preview-3-android-apk-download/) and it works fine, but the UI is the old one.
Also you get the notification in the Play Store to update it, which brings the new UI and brokes video recording, so I think something is still wrong.
Sadly I can't install MM back to check what google camera version I had since I need to attend important stuff this days with phone. I'm getting a new phone someday next week(in like 1 to 3 days) and I will be able to gladly help you guys to test stuff.
Click to expand...
Click to collapse
It's because from v3 GoogleCamera uses API2. On marshmallow this was fine. Android 7.x's camera framework hardening prevents us from using it without HAL changes or framework hacks.
To sum up google camera version that I use on Nougat
- 2.7.008 hdr+ ok. Video rec ok
- 3.2.045 hdr+ ok. Video rec not ok ( this version is the last for N5 on MM with no issues in video rec)
- 4.1.006 hdr+ not ok. Video recording not ok
Hdr+ not ok meaning no processing done. No difference of output between non hdr+ and hdr+ photos
amnher said:
To sum up google camera version that I use on Nougat
- 2.7.008 hdr+ ok. Video rec ok
- 3.2.045 hdr+ ok. Video rec not ok ( this version is the last for N5 on MM with no issues in video rec)
- 4.1.006 hdr+ not ok. Video recording not ok
Hdr+ not ok meaning no processing done. No difference of output between non hdr+ and hdr+ photos
Click to expand...
Click to collapse
With my latest patches we can go up to 3.1.x.
After a lot of debug, now i'm relatively sure what causing the problem, but i needed to stop development. Because my phone is accidentally dropped into water and now it's dead
Sorry guys
@kamarush
too bad you're one hell of developer like the old days when I was still on xperia mini(Smultron) well hope someone can continue your work
kamarush said:
With my latest patches we can go up to 3.1.x.
After a lot of debug, now i'm relatively sure what causing the problem, but i needed to stop development. Because my phone is accidentally dropped into water and now it's dead
Sorry guys
Click to expand...
Click to collapse
Willing to share? Thanks in advance.
JulianXhokaxhiu said:
Willing to share? Thanks in advance.
Click to expand...
Click to collapse
Just check his github
First of all, we need to port this commit. this would have been my next step.
https://android.googlesource.com/platform/hardware/qcom/camera/+/ecc5ece9eff7c7855faf676881d0aba59c1bd1db%5E!/
Then we can check things further.
It's fixed in Dark's 7.1 CM14.1 ROM. Using 4.2 without issue. Haven't confirmed for sure if HDR+ is working properly, but from the extra delay after taking a shot I'd guess it is.
snives said:
It's fixed in Dark's 7.1 CM14.1 ROM. Using 4.2 without issue. Haven't confirmed for sure if HDR+ is working properly, but from the extra delay after taking a shot I'd guess it is.
Click to expand...
Click to collapse
No it's not. That's only a workaround (hack) for mediaserver and cameraserver.
We can deal with the real problem, as we have the complete source for camera and media/display. Just need a real developer who understand bufferqueue, native_ and buffer_handle_t functions and gralloc. To continue my work.
So, workarounds are not real fixes imo.
kamarush said:
No it's not. That's only a workaround (hack) for mediaserver and cameraserver.
We can deal with the real problem, as we have the complete source for camera and media/display. Just need a real developer who understand bufferqueue, native_ and buffer_handle_t functions and gralloc. To continue my work.
So, workarounds are not real fixes imo.
Click to expand...
Click to collapse
why do u need that?
the latest camera with the latest hal is working!
Sent from my Nexus 5 CAF using Tapatalk
santi1993 said:
why do u need that?
the latest camera with the latest hal is working!
Sent from my Nexus 5 CAF using Tapatalk
Click to expand...
Click to collapse
The point is, we have the whole source. Hal3 can be fixed without "dirty" patches on fw to stay clear the source.
These workarounds completely disables a huge size of the security measures introduced by Google in N.
These only for devices which don't have access to Camera HAL or encoder sources, or has old blobs.
Btw for temporary solution is good, but need to patch up correctly the HAL.
Hello Everyone,
A few days ago, I purchased the Redmi Note10s, which worked very fine in every aspect of the smartphone, but I've found issues of video rendering in apps like YouTube and others even in 1080P.
But The Strange thing is that while playing the same video on the youtube website using Firefox browser it renders perfectly and Amazing.
Below I've attached the screenshot of the same video playing in those two different apps.
YOUTUBE:
As You'll see below the SS of the YouTube Sample is Over sharped and isn't pleasing to the eyes
FIREFOX:
In the samples of Firefox, it renders the way we want with perfect colours and sharpening.
Is this problem with Software or GPU rendering, I don't know. If anyone having this phone please share your opinions or thoughts on this, and also let me know if anyone facing the same issue.
P.S: this is my first post on XDA community, hoping XDA community will help with this problem.
i have the same issue ... i sent it to mi store to check it up for a few days and they said it was alright ...
i also checked another note 10 s device in the store .. it has the same issue
the issue exist in youtube and google chrome ....
not sure if its a software issue that will be fixed or bad qc
since u posted 20 days ago .. did u do anything about this issue ?
I have come across the thing called video decoding, which is done mainly by GPU or processor. In our phone, a MediaTek processor is used which is using a technology called MiraVision to render the HDR video which causing the issue while playing video in lower quality like 480P. Some solutions I found on Reddit is saying to disable the hardware overlays to solve the issue, as this problem already faced by redmi note 8 users. But didn't solve our issue.
But idk why I'm used to this as video of 720P is much sharper and feels good now
i kinda like it although it might have to do something with miravision
best is to ask people using realme 7 and redmi note 8
b1boi said:
i kinda like it although it might have to do something with miravision
best is to ask people using realme 7 and redmi note 8
Click to expand...
Click to collapse
Try to instal Activity Launcher then search "AI HDR Enhancement" under "Settings" then turn it off
Try youtube vanced. No such issue with it.
GildroY said:
Try youtube vanced. No such issue with it.
Click to expand...
Click to collapse
I am using YouTube vanced still face the issue
pravin_pran said:
I am using YouTube vanced still face the issue
Click to expand...
Click to collapse
Not sure then ... Its fine with my device so far.
GildroY said:
Try youtube vanced. No such issue with it.
Click to expand...
Click to collapse
Which version of youtube vanced are you using???
It's already off but found that it's a Issue regarding the super resolution option but there's no way to disable it.
HanzoLaura said:
Try to instal Activity Launcher then search "AI HDR Enhancement" under "Settings" then turn it off
Click to expand...
Click to collapse
Karan Munjani said:
Which version of youtube vanced are you using???
Click to expand...
Click to collapse
16.20.35
It maybe an issue with MiUI's VP9 renderer (VP9 is a new codec developed by Google as a free alternative to HEVC ,or H265).
The codec is used by default by YouTube since it offers higher compression compared to previously used H264 codec (AVC).
The codec is all fine, and it is absolutely recommended to use it since it offers better clarity and saves data at the same time.
The problem is with MiUI's VP9 rendering algorithm which is over-sharpening the video. I suggest you to contact Xiaomi to fix the issue, and disable VP9 in YouTube Vanced for time being.
If the above solution didn't work, you may try changing the decoder in MX Player [Try all 3 decoders - HW, HW+, and SW.]
If you don't observe any changes, use the mx_aio custom codec.
MX Player Custom Codec [AC3,DTS,MLP,TRUEHD, etc..]
https://github.com/USBhost/MX_FFmpeg is my modified source where i'm building from You can download recent codecs here ( GitHub releases ) and 1.35.0-1.8.6 here ( Google Drive ). Also the XDA download tab is no longer updated as for some reason I...
forum.xda-developers.com
Pls reply if this worked or not, so that others would benefit.
Has this been fixed? is it even fixable via firmware updates?
As far as i know the Redmi Note 8 Pro has the same problem and still has it to this day
I was going to pick this phone up for my mother by this is definitely a turn off
pravin_pran said:
I am using YouTube vanced still face the issue
Click to expand...
Click to collapse
try chaging the codec override in vanced setting , also to enable extra options in the override menu tap many times on about to unlock hidden setting
Begonia user here. .as for most possible fix
change "ro.vendor.mtk_pq_support" from 2 to 0 (in Vendor/Build.prop)
*well, it need root access to do that.
I also have the same problem on JMGO O1 projector. Every time I play another video I have to go into settings and adjust the sharpness, from 0 to 1 then back to 0.
[MIRAVISION] Steps to tweak or disable Mediatek MiraVision Hardware Video Decoder Over-processing™
Mediatek Miravision Hardware Video Decoding is found on several Mediatek Chipsets and vendors like Xiaomi design devices for users worldwide that neither allow nor show the settings to configure their media experience to their preference or...
forum.xda-developers.com