Hey guys,
Long time lurker, but just wanted to share this as a quick fix for people struggling with the bluetooth streaming audio quality issues that Google still hasn't fixed in 4.3. I've been reading through one of the open issues at Google:
http://code.google.com/p/android/issues/detail?id=39632
and found in post #157 that someone noticed this commit elsewhere that supposedly fixed the low quality issue:
https://github.com/djp952/android-p...mmit/2ee778598e3b2e3f826e3f6b4eeafbb11005b21b
All credit to the people who found all this information in the first place, but I've been so tired of this stupid quality thing that I downloaded the source for 4.3 and tried to toss this one line in there to see what would happen. Long story short, I built the JSS15J branch for mako and it seems to have -vastly- improved the quality (back up to where CM was to my ears, at least).
Afaik, all you have to do is backup and replace these two files living in system/lib/hw and set permissions to 644. Then reboot and all should be well - with the added benefit of AVRCP 1.3 working too now.
Please don't be to harsh if I've forgotten something crucial... it's my first time sharing anything at all
UPDATE:
I've uploaded a different set of files built with DEFAULT_SBC_BITRATE=345 (mako-JSS15J-345-btaudio.zip). The original was set with DEFAULT_SBC_BITRATE=328 (mako-4.3-JSS15J-btaudio.zip). Those of you who were having issues with stuttering...maybe this will fix it? I have no idea...not a real developer But give it a shot!
UPDATE #2:
From the sounds of things, these files are only compatible with AOSP compiled roms - no one's gotten it to work with CM10.2 yet, I believe. Just fair warning if it doesn't work for ya.
Cbaronne, this particular issue has been such a pain as I'm a heavy music listener in the car so I'm excited to see this.
However, any idea if this work on JWR66V?
As I understand it, the difference between the two are mainly wifi related so I'm willing to guess that those two files would be the same.
Your thoughts?
AdamUpNorth said:
Cbaronne, this particular issue has been such a pain as I'm a heavy music listener in the car so I'm excited to see this.
However, any idea if this work on JWR66V?
As I understand it, the difference between the two are mainly wifi related so I'm willing to guess that those two files would be the same.
Your thoughts?
Click to expand...
Click to collapse
I originally compiled JSS15S because I had aspirations of running a clean new build to test the WiFi stuff, but then just took those two files out to try 'em. I'm on stock 66V rooted and they work just fine for me ^^
You Da Man.
Trying this right now.
UPDATE: Works like a charm. No more nasty hissing/crackling of the higher frequencies. Sounds great. Thank you sir, you just made my week.
I'm using the same files extracted from GNex factory image and is working great. However I think I may be missing BLE as GNex doesn't support it. I will give this a try and report back.
Thanks for this. I upgraded to 66V from AOKP the other day & have been seriously considering going back due to the horrible highs (listen to some dubstep and you won't be able to focus on anything else.)
Here's a flashable zip I made. Don't mind the updater script I just used one from another zip I had I my phone that mounted
http://db.tt/LZPJNzjV
Sent from my Nexus 4 using xda app-developers app
getting quite a few glitches using this. audio seems to randomly stutter like its being stretched; may have something to do with cpu speed scaling not sure yet.
quality does sound better tho with this.
That happened to me too initially when I was playing with GNex files. Try repairing the device.
---------- Post added at 12:03 PM ---------- Previous post was at 11:32 AM ----------
Just tested this. Working great.
Does AVRCP 1.3 really work? For me, it looks like this in the image appended ... trackname + album working fine, but band does not
I get track number, time played, artist, track name and album name on a cheap sony car stereo unit.
As for sound quality I don't really have a reference point so haven't noticed it being all that bad. If I wanted to flash the attached zip how easy is it? The limit of my experience flashing was a stock 4.3 using this tutorial http://forum.xda-developers.com/showthread.php?t=2010312
Thanks for supplying this patch. It works excellently
I've noticed though that last.fm scrobbler can't 'see' what Play Music is playing anymore though, reckon the patched file breaks that connectivity?
noobdeagle said:
getting quite a few glitches using this. audio seems to randomly stutter like its being stretched; may have something to do with cpu speed scaling not sure yet.
quality does sound better tho with this.
Click to expand...
Click to collapse
I've never personally experienced the stutter problem, but afaik, that's an ongoing issue that other people have reported (and perhaps why Google still hasn't made this small change). I know it isn't perfect yet, so while waiting for CM10.2 I'm keeping my eyes open for other tweaks to that file
muff99 said:
Does AVRCP 1.3 really work? For me, it looks like this in the image appended ... trackname + album working fine, but band does not
Click to expand...
Click to collapse
I've only ever used this fix with Play Music so far, and it all seems to be working (at least artist/title/album). I don't have a lot of experience with the new Bluetooth stack outside of that x.x
Thanks for the fix! The audio quality is much improved, and the AVRCP stuff still works completely. I was going to make a CWM zip of this, but someone earlier in the thread beat me to it.
Thanks!
Edit: I'm using Google Play Music, which seems to work very well with AVRCP. I can't speak for other players.
cbaronne said:
I've never personally experienced the stutter problem, but afaik, that's an ongoing issue that other people have reported (and perhaps why Google still hasn't made this small change). I know it isn't perfect yet, so while waiting for CM10.2 I'm keeping my eyes open for other tweaks to that file
Click to expand...
Click to collapse
Darn. I'm getting the occasional shutter as well. Although, I'd much rather deal with the odd stutter than terrible audio 100% of the time.
Looks like google is having the same issues. See post #182 https://code.google.com/p/android/issues/detail?id=39632#c182
cbaronne, could I bother you to create another set of files using the max bitrate of 345 for 48Khz? After reading the comments on the Google code site and from here (http://soundexpert.org/news/-/blogs/bluetooth-audio-quality-a2dp), I'm curious to see what happens.
AdamUpNorth said:
Darn. I'm getting the occasional shutter as well. Although, I'd much rather deal with the odd stutter than terrible audio 100% of the time.
Looks like google is having the same issues. See post #182 https://code.google.com/p/android/issues/detail?id=39632#c182
cbaronne, could I bother you to create another set of files using the max bitrate of 345 for 48Khz? After reading the comments on the Google code site and from here (http://soundexpert.org/news/-/blogs/bluetooth-audio-quality-a2dp), I'm curious to see what happens.
Click to expand...
Click to collapse
Sure thing - now I'm curious too. Changed that value to 345 and kicked off the build... will have something to post when I get home from work!
Edited my post with a more friendly link for the flashable zip.
Sent from my Nexus 4 using xda app-developers app
I just ended building JSS15J just to get this fixed and found this post lol... an incredibly annoying bug and an easy workaround. Thanks for posting it.
muff99 said:
Does AVRCP 1.3 really work? For me, it looks like this in the image appended ... trackname + album working fine, but band does not
Click to expand...
Click to collapse
If I use Pandora I have the same issue:
Artist shows up in the song name field on my car radio
Album shows up correctly
Song Title is missing
If I use Google Play Music everything shows up correctly.
So it's been about 2 months since I recieved my Remix Mini and I really like it. The biggest reason is access to Google Play games and apps on the desktop. But a big dealbreaker for me is that Google Play Music doesn't work. I saw in Jide Support that they were working on fixing it back in December and I'd like to know what has been done to fix this since then.
Hey,
May I ask more contextual details about the issue you are referring? Some of reported issues of Google Play Music have been solved in Version 2.0.111. For the best experience, please always make sure your Remix OS is on the latest version.
Cheers
Cameron
Yes, I am on version 2.0.111 and Google Play Music still will not play anything.
Our engineering team is working on a fix around this issue. We will release this fix soon.
nbieter said:
Yes, I am on version 2.0.111 and Google Play Music still will not play anything.
Click to expand...
Click to collapse
I'm on v2.0.111 and Google Play Music works fine for me. I'm playing my music right now. Maybe there's something unique about your setup?
google music streaming is working, but please explain whats not working 4 you
I'm on Version 2.0.203 and it seems to work on my mini
I Also have it set up on my Dads surface pro 3 i will try it this weekend
The 2.0.23 update fixed it for me, thanks everybody.
I just got a Redmi Note 11. When trying to play a 10bit 265 (HEVC) encoded video the playback was choppy and not smooth. MX Player claims "HW decoding is unsupported" for that format. Trying to force it through the settings did not help. Other video players such as VLC did not fare any better. I found this really strange as my old Redmi Note 4 from 2017 played these videos without a problem.
Digging into it a looked up the Snapdragon 680 that powers the device, and according to what I found the CPU has support for 10bit h265 (source: https://www.cpu-monkey.com/en/cpu-qualcomm_snapdragon_680_4g). So what is going on here? Am I doing something wrong or did Xiaomi somehow cheap out on the phone? I am really disappointed by my purchase at the moment as 10bit video is something I use a lot, so any ideas for solving this will be much appreciated.
(Note: I posted a similar question over here: https://forum.xda-developers.com/t/...hevc-discussion.2725241/page-42#post-87053885 but since I got no answer I thought I'd try to get help here, and if not at least warn people of buying the phone as the lack of support is not listed anywhere. If my double post is against the rules I apologize)
magman2 said:
I just got a Redmi Note 11. When trying to play a 10bit 265 (HEVC) encoded video the playback was choppy and not smooth. MX Player claims "HW decoding is unsupported" for that format. Trying to force it through the settings did not help. Other video players such as VLC did not fare any better. I found this really strange as my old Redmi Note 4 from 2017 played these videos without a problem.
Digging into it a looked up the Snapdragon 680 that powers the device, and according to what I found the CPU has support for 10bit h265 (source: https://www.cpu-monkey.com/en/cpu-qualcomm_snapdragon_680_4g). So what is going on here? Am I doing something wrong or did Xiaomi somehow cheap out on the phone? I am really disappointed by my purchase at the moment as 10bit video is something I use a lot, so any ideas for solving this will be much appreciated.
(Note: I posted a similar question over here: https://forum.xda-developers.com/t/...hevc-discussion.2725241/page-42#post-87053885 but since I got no answer I thought I'd try to get help here, and if not at least warn people of buying the phone as the lack of support is not listed anywhere. If my double post is against the rules I apologize)
Click to expand...
Click to collapse
Try using mpv for Android (also built for Windows & Linux) -- it also supports multiple audio and subtitle tracks:
https://apkpure.com/mpv-android/is.xyz.mpv
https://play.google.com/store/apps/details?id=is.xyz.mpv
Oifan said:
Try using mpv for Android (also built for Windows & Linux) -- it also supports multiple audio and subtitle tracks:
https://apkpure.com/mpv-android/is.xyz.mpv
https://play.google.com/store/apps/details?id=is.xyz.mpv
Click to expand...
Click to collapse
Thanks for the reply. I just tried the app you suggested, and it too won't let me set it to hardware decoding. Pressing the SW button does nothing. So it seems no app is able to use hardware acceleration on 10bit 265 videos. Whether that is due to some driver issues (?) or a physical lack of support in the CPU is still unclear.
Am I the only one with this issue?
magman2 said:
Thanks for the reply. I just tried the app you suggested, and it too won't let me set it to hardware decoding. Pressing the SW button does nothing. So it seems no app is able to use hardware acceleration on 10bit 265 videos. Whether that is due to some driver issues (?) or a physical lack of support in the CPU is still unclear.
Am I the only one with this issue?
Click to expand...
Click to collapse
I think this is a problem of your Android OS -- I have just tested the x265 – Tears Of Steel 1080P @ 400kbps sample HEVC video (top left here: https://x265.com/hevc-video-files/) in mpv player (on my Xiaomi spesn) -- and I could toggle the [HW] button without problems.
I am running Android 12L - SuperiorOS, download links here:
Redmi Note 11 Updates
#SuperiorOS #Spes #UnOfficial #SL #OSS #Spesn SuperiorOS Unofficial | Android 12L Build date: 13/6/'22 ▪️Download ▪️Support Group Changelog: •Initial build. Known Bugs: •NFC •U find a bug, u can tell me Notes: •Use Mind GApps Credits & Thanks: @dblenk9 & @jabiyeff21 for trees By...
t.me
Oifan said:
I think this is a problem of your Android OS -- I have just tested the x265 – Tears Of Steel 1080P @ 400kbps sample HEVC video (top left here: https://x265.com/hevc-video-files/) in mpv player (on my Xiaomi spesn) -- and I could toggle the [HW] button without problems.
I am running Android 12L - SuperiorOS, download links here:
Redmi Note 11 Updates
#SuperiorOS #Spes #UnOfficial #SL #OSS #Spesn SuperiorOS Unofficial | Android 12L Build date: 13/6/'22 ▪️Download ▪️Support Group Changelog: •Initial build. Known Bugs: •NFC •U find a bug, u can tell me Notes: •Use Mind GApps Credits & Thanks: @dblenk9 & @jabiyeff21 for trees By...
t.me
Click to expand...
Click to collapse
That file my phone can play as well, but that file is an 8 bit file. It's the 10 bit encodes that the phone won't play with hardware acceleration. Can you try this file and say if you have hardware acceleration? I tested this file on my old Redmi Note 4 and it played back smoothly. My new Note 11 can't handle it:
https://jell.yfish.us/media/jellyfish-10-mbps-hd-hevc-10bit.mkv
Also, for the record, I am using the stock MIUI 13.
magman2 said:
That file my phone can play as well, but that file is an 8 bit file. It's the 10 bit encodes that the phone won't play with hardware acceleration. Can you try this file and say if you have hardware acceleration? I tested this file on my old Redmi Note 4 and it played back smoothly. My new Note 11 can't handle it:
https://jell.yfish.us/media/jellyfish-10-mbps-hd-hevc-10bit.mkv
Also, for the record, I am using the stock MIUI 13.
Click to expand...
Click to collapse
You are right about the bpp -- my sample MP4 has bitdepth=8 in the header, while your sample MKV has bitdepth=10 in the header.
I have just tried your sample on my SuperiorOS (build 20220613-0631), and:
mpv starts in SW-render mode and cannot switch to HW-render mode,
X-plore will just show black screen with message: Internal codec error
I guess that means that:
either the underlying hardware does not have the required decoder,
or the driver for that hardware does not support this video format.
Oifan said:
You are right about the bpp -- my sample MP4 has bitdepth=8 in the header, while your sample MKV has bitdepth=10 in the header.
I have just tried your sample on my SuperiorOS (build 20220613-0631), and:
mpv starts in SW-render mode and cannot switch to HW-render mode,
X-plore will just show black screen with message: Internal codec error
I guess that means that:
either the underlying hardware does not have the required decoder,
or the driver for that hardware does not support this video format.
Click to expand...
Click to collapse
Thank you again for taking time to test and respond.
I find the lack of hardware support (if that is indeed the issue) to be very surprising. The 680 is a 2022 chip. not supporting a popular encoding format these days just seems so unlikely and strange. It's also not something I thought I have to check before I buy a phone, and even if i would look it up I would find that it does support it.
If it is a driver issue, than who is responsible? Qualcomm or Xiaomi? And is there any way of fixing it? (i.e. some sort of custom driver or official update)
magman2 said:
Thank you again for taking time to test and respond.
I find the lack of hardware support (if that is indeed the issue) to be very surprising. The 680 is a 2022 chip. not supporting a popular encoding format these days just seems so unlikely and strange. It's also not something I thought I have to check before I buy a phone, and even if i would look it up I would find that it does support it.
If it is a driver issue, than who is responsible? Qualcomm or Xiaomi? And is there any way of fixing it? (i.e. some sort of custom driver or official update)
Click to expand...
Click to collapse
I strongly believe it's just an issue of the Adreno 610 driver (so it will be fixed in a couple of days / weeks) -- check these 3 relevant info-pages:
https://www.gsmarena.com/xiaomi_redmi_note_11-11336.php
https://www.cpu-monkey.com/en/igpu-qualcomm_adreno_610-231
https://cpu-comparison.com/igpu/qualcomm-adreno-610/
Regarding who will fix it -- I believe it should be Google with the help of Xiaomi / Qualcomm.
Oifan said:
I strongly believe it's just an issue of the Adreno 610 driver (so it will be fixed in a couple of days / weeks) -- check these 3 relevant info-pages:
https://www.gsmarena.com/xiaomi_redmi_note_11-11336.php
https://www.cpu-monkey.com/en/igpu-qualcomm_adreno_610-231
https://cpu-comparison.com/igpu/qualcomm-adreno-610/
Regarding who will fix it -- I believe it should be Google with the help of Xiaomi / Qualcomm.
Click to expand...
Click to collapse
I really hope you are right, although I am assuming this issue was present since the phone launched and it still has not been fixed after a few months. At least I now have hope that it can be fixed.
There are other phones that equipped with Snapdragon 680 4G, I wonder if they can play HEVC 10bit videos with hardware acceleration. Hope it can be fixed too.
lovinamn said:
There are other phones that equipped with Snapdragon 680 4G, I wonder if they can play HEVC 10bit videos with hardware acceleration. Hope it can be fixed too.
Click to expand...
Click to collapse
Going by the list here: https://www.notebookcheck.net/Qualc...-Processor-Benchmarks-and-Specs.611368.0.html there seems to be several phones using that chip, and I could not find a mention of anyone with an issue online. That does not mean that there is no issue, after all I couldn't find any mention of the problem on the Redmi Note 11 until I posted it here, and that phone has been out for several months already. If, as the poster above suggested, the video decoder is part of the GPU and not the CPU, then the list of devices with an Adreno 610 is even larger (https://www.notebookcheck.net/Qualcomm-Adreno-610-GPU-Benchmarks-and-Specs.434054.0.html), and I can't find any mention of an issue with those devices either.
Basically what I am trying to say is that the problem seems to be a Note 11 problem, but for some reason nobody posted anything anywhere until now. So we need people with any of the similar devices to report if by them hardware decoding is present. Meanwhile I contacted Xiaomi and so far they told me to use a third party video player if the built in app does not play my desired format. I'll report back if/when they start being more helpful.
magman2 said:
That file my phone can play as well, but that file is an 8 bit file. It's the 10 bit encodes that the phone won't play with hardware acceleration. Can you try this file and say if you have hardware acceleration? I tested this file on my old Redmi Note 4 and it played back smoothly. My new Note 11 can't handle it:
https://jell.yfish.us/media/jellyfish-10-mbps-hd-hevc-10bit.mkv
Also, for the record, I am using the stock MIUI 13.
Click to expand...
Click to collapse
Hello. I downloaded and played the video on my Note 11 in VLC. I didn't have any problems playing it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
N0b0dyy said:
Hello. I downloaded and played the video on my Note 11 in VLC. I didn't have any problems playing it.
View attachment 5645007
Click to expand...
Click to collapse
It plays totally smoothly? By me this file stutters like crazy in VLC.
How about MX Player? Does it let you select hardware acceleration? (the HW button in thew corner)
Yes it plays totally smoothly in VLC. I have tried MX player and there it stutters sometimes. And I tried selecting HW decoding and it showed that its not supported.
I am currently not on MIUI but on a custom rom.
N0b0dyy said:
Yes it plays totally smoothly in VLC. I have tried MX player and there it stutters sometimes. And I tried selecting HW decoding and it showed that its not supported.
I am currently not on MIUI but on a custom rom.
Click to expand...
Click to collapse
Interesting. In other files I tried - all of which had a lower bitrate than the jellyfish file - VLC was able to hit mostly smooth playback, while MX Player still stuttered a bit.
So my conclusion: VLC has better software decoding than MX Player. Meanwhile, whatever rom you are using is more performant than MIUI, which allows the video players to squeeze more out of the CPU in software decoding compared to my phone which is running MIUI. Still, even by you, the underlying problem remains: hardware decoding is unavailable, which is unacceptable.
As a side note, update on my attempts to get some sort of acknowledgement from Xiaomi about the issue: I sent several emails to their support address. Somewhat surprisingly they responded to all of them, but in none of their responses did they admit there is a problem. They mostly deflected and gave me uncommitted generic answers (i.e. "try a third party video player" or "the Xiaomi devices supports MPEG4, H.264/AVC, H.263/3GP and RMVB and other video formats. With the development of technology, the usage of some uncommon video formats has declined, and most mobile phones on the market support common formats such as MP4"). I also reported the issue on the built-in feedback option. Not too hopeful about that either, but at least that one should reach an actual developer.
Anyway, if anyone has an idea of something else to try, or some sort of fix for the problem I'd be happy to hear.
magman2 said:
Interesting. In other files I tried - all of which had a lower bitrate than the jellyfish file - VLC was able to hit mostly smooth playback, while MX Player still stuttered a bit.
So my conclusion: VLC has better software decoding than MX Player. Meanwhile, whatever rom you are using is more performant than MIUI, which allows the video players to squeeze more out of the CPU in software decoding compared to my phone which is running MIUI. Still, even by you, the underlying problem remains: hardware decoding is unavailable, which is unacceptable.
As a side note, update on my attempts to get some sort of acknowledgement from Xiaomi about the issue: I sent several emails to their support address. Somewhat surprisingly they responded to all of them, but in none of their responses did they admit there is a problem. They mostly deflected and gave me uncommitted generic answers (i.e. "try a third party video player" or "the Xiaomi devices supports MPEG4, H.264/AVC, H.263/3GP and RMVB and other video formats. With the development of technology, the usage of some uncommon video formats has declined, and most mobile phones on the market support common formats such as MP4"). I also reported the issue on the built-in feedback option. Not too hopeful about that either, but at least that one should reach an actual developer.
Anyway, if anyone has an idea of something else to try, or some sort of fix for the problem I'd be happy to hear.
Click to expand...
Click to collapse
I would recommend you to try to play several 10-bit videos + several 8-bit videos in mpv player (https://apkpure.com/mpv-android/is.xyz.mpv) and make screenshots of the bottom control panel when playing them -- see my screenshots below.
Then you can explain that for the 10-bit videos it's impossible to toggle the HW/SW rendering button and claim that you believe it's because of the present Adreno 610 driver is only supporting h265/HEVC(8-bit) and not 10-bit video streams (although the GPU supports it --> https://www.cpu-monkey.com/en/igpu-qualcomm_adreno_610-231).
Oifan said:
I would recommend you to try to play several 10-bit videos + several 8-bit videos in mpv player (https://apkpure.com/mpv-android/is.xyz.mpv) and make screenshots of the bottom control panel when playing them -- see my screenshots below.
Then you can explain that for the 10-bit videos it's impossible to toggle the HW/SW rendering button and claim that you believe it's because of the present Adreno 610 driver is only supporting h265/HEVC(8-bit) and not 10-bit video streams (although the GPU supports it --> https://www.cpu-monkey.com/en/igpu-qualcomm_adreno_610-231).
Click to expand...
Click to collapse
Thanks for the suggestion. I actually attempted something similar. I sent them a screen recording of the issue, including the stuttering video and the error message it shows every time I try to set it to HW. Unfortunately, they refuse to acknowledge the issue at all, and keep giving me those vague answers. I also sent the video as part of my report in the feedback app, but I have no way of knowing if anyone will look at it.
Meanwhile, I decided to try a slightly different tactic. Using a new email address I sent their support an email saying I want to buy a Note 11, but I was wondering if it has hardware decoding for 10 bit hevc. Their response: "we regret to inform you that as of now we don't have any official information regarding this. Generally speaking, Redmi series phones will support common video decoding methods in the market, but lesser used decoding methods are not included for the time being." It seems they just will not commit to any answer no matter how you ask it. You'd think a company would know what their product can do.
magman2 said:
Thanks for the suggestion. I actually attempted something similar. I sent them a screen recording of the issue, including the stuttering video and the error message it shows every time I try to set it to HW. Unfortunately, they refuse to acknowledge the issue at all, and keep giving me those vague answers. I also sent the video as part of my report in the feedback app, but I have no way of knowing if anyone will look at it.
Meanwhile, I decided to try a slightly different tactic. Using a new email address I sent their support an email saying I want to buy a Note 11, but I was wondering if it has hardware decoding for 10 bit hevc. Their response: "we regret to inform you that as of now we don't have any official information regarding this. Generally speaking, Redmi series phones will support common video decoding methods in the market, but lesser used decoding methods are not included for the time being." It seems they just will not commit to any answer no matter how you ask it. You'd think a company would know what their product can do.
Click to expand...
Click to collapse
Wow, you are quite resourceful I must say -- nice move...
To me it looks like the development team (in Xiaomi / Google) is either behind schedule or can't keep up with the latest video formats -- so they are just bouncing emails like yours with a standard "not included for the time being" response.
Hopefully there will be more displeased (potential) customers complaining about this, creating sufficient pressure on these corporations so that they will be sufficiently motivated to add the missing codec support to the current graphics driver -- I guess this issue isn't only with Adreno 610, but with some other GPUs as well.
However, adding features to a graphics driver on any OS is a tricky thing -- they need to test the new driver thoroughly so that these additions won't cause any crashes... Meaning it will take some weeks or even months from the moment they decide to add this feature.
Official Firmware of RN11 had this problem for me, I installed Custom ROMS and Problem was solved for most part. Movies from PSArips run smoothly on Mi Video especially. Some 10 bit videos higher bitrate struggle sometime when trying to fast forward.
tsdq512 said:
Official Firmware of RN11 had this problem for me, I installed Custom ROMS and Problem was solved for most part. Movies from PSArips run smoothly on Mi Video especially. Some 10 bit videos higher bitrate struggle sometime when trying to fast forward.
Click to expand...
Click to collapse
That does not really sound like you solved the problem. Instead you are mostly brute forcing your way through with software decoding. Struggling when trying to fast forward is not something I find acceptable in a modern phone, especially one that has the hardware to play it properly, and in no place did the manufacturer communicate the issues on the RN11. Meaning there is no reason to assume the phone will not support it. I tested hardware decoding on the Redmi Note 4, 8, 9 and 10 and they all play it with no problem.