Restore missing LDAC Bluetooth profile - Huawei MediaPad M5 Questions & Answers

For reasons only know to Huawei, they have removed the LDAC high quality audio option, which is standard in Oreo.
It works fine in lineage 15.1 beta 5 but missing from stock. Anyone know of a magisk module to restore it?
Missing LDAC on my don't headphones and it's a big jump back in quality to aptxhd

Would also like to know if this is possible...

Related

Oreo users, Any news on aptx or LDAC?

Dear users who already decided to try Oreo roms, have you seen any settings related to Bluetooth codecs? Any signs of aptx or LDAC codecs?
Yes, seen but not tried.
Rishabh1x said:
Yes, seen but not tried.
Click to expand...
Click to collapse
Thank you. Can you report later if it's working or not?
LDAC works
mehrshad.shafaghi said:
Dear users who already decided to try Oreo roms, have you seen any settings related to Bluetooth codecs? Any signs of aptx or LDAC codecs?
Click to expand...
Click to collapse
Don't know sure about aptX as i didn't feel the difference in quality, but i can confirm that LDAC is working on Nitrogen OS (in pretty much all versions since it came out with Oreo). I am using the Sony MDR 1000X and it uses LDAC by default now, after oreo update. You can also manually change the codec from Bluetooth settings (turn LDAC on off for that audio device) or through developer settings, where you can choose the codec and even the bitrate, sampling rate etc etc. And it changes on the fly, so you can really feel the difference. LDAC is well worth it. But I've seen that on the highest quality, you need to be close to your device, else the sound can drop out sometimes.
agambhandari said:
Don't know sure about aptX as i didn't feel the difference in quality, but i can confirm that LDAC is working on Nitrogen OS (in pretty much all versions since it came out with Oreo). I am using the Sony MDR 1000X and it uses LDAC by default now, after oreo update. You can also manually change the codec from Bluetooth settings (turn LDAC on off for that audio device) or through developer settings, where you can choose the codec and even the bitrate, sampling rate etc etc. And it changes on the fly, so you can really feel the difference. LDAC is well worth it. But I've seen that on the highest quality, you need to be close to your device, else the sound can drop out sometimes.
Click to expand...
Click to collapse
Thanks for making effort and clearing things up.
LDAC is working perfectly on my OP3T with OS Beta 16.
Viper4android doesnt work though when headphones are connected with LDAC. I am using MDR-100ABN. Thye have LDAC and OP3T is streaming perfectly on that codec.
When I use my Jaybird X2s, codec switches to SBC automatically. Viper4android works on my X2s. I am not seeing AptX option in developer settings.

aptx support?

greetings. Does the mediapad m5 support aptx or other high quality bluetooth codecs? Thanks!
"It does..." Well it's listed in the developer settings, however each time I enable one of them it reverts back to the default one... Maybe I am doing something wrong, but I could not get it working.
Also, keep in mind that wifi and Bluetooth don't work well together.
Yes it does, I like the sound from my m5 more than from s9, when it comes to Bluetooth performance. I played with s9 settings but couldn't come to the sound m5 gives via Bluetooth. Don't even know why they are sound so different.
Aptx and aptx HD are listed in the developers option. But I have no compatible devices to test it. I have a Sony AVR that has LDAC but it appears the M5 doesn't have LDAC codec integrated, even though it should be baked in Android Oreo.
thanks for your answers!

[INFO] N Dolby port with V4A setup on custom 8.1

There's a Nougat Dolby port confirmed working on 8.1 ROMs. Thanks to @roisuke guide (and permission to repost for info) on the LOS15.1 thread summarising steps similar to the original Pixel 2XL guide, which uses the old ARISE N Dolby Atmos zip. In roisuke's post, his/her reason for trying this old Dolby is the newer Dolby boot loops on LOS15.1. In my case I was looking for a better compatible and audio quality Dolby when I found out about it. There's a few reasons i'll group into headings below. I know Dolby speakers that we paid for on stock for our device is a loved feature sought by more than just a few of us. I hope to help improve some people's speaker audio experience like I have, finally rivaling stock performance with V4A extra on top :laugh:
For installation instructions I'll just link roisuke's post, as mine has more to do with settings and usage explanation. I will just add that I had a different issue installing that Dolby zip on RR-O, the process would freeze without an error, requiring a force restart. The zip isn't detected by Magisk Manager and so can't be installed there. I couldn't install the zip when any Magisk version is installed. I ended up having to uninstall Magisk to allow the zip to install to system and then follow up with the other Magisk audio mods installed normally, Viper4Android (i'm on the old 2.3.4.0 for it's Super driver and better graphic equaliser), Ainur Sauron (optional maybe, it claims to improve audio in system and targets Axon 7 as well, I haven't tested this mod without it yet) and lastly Audio Media Library. Also thanks to @Oki for pointing out the hifi DAC patch is necessary with this particular Dolby mod.
Nougat Dolby sounds better
The reasoning is that I've recently been testing custom ROM N Dolby and it sounds just as good as stock N had. While I tested Oreo Dolby ports back when the B32+B10 bootstack was new also just recently too and found it didn't sound as good as N's. Therefore I understand it's not a custom port issue that the new O Dolby sounds worse than N but that it's the updated Dolby itself.
It can work together with V4A
A benefit of this old N Dolby is it is working with current V4A whereas I can't seem to get the new O Dolby to run with V4A, it did when I tested months ago but I can't recreate that either. A benefit to using V4A in combination is it's "Firequalizer" to preset "Small Speakers" accentuates bass and lessens the tinny treble, this is something I used to do back on stock N as well.
It can be configured to set and forget
A little talked about but great feature of stock Dolby is it remembered the settings separately for plugged/unplugged and for each individual app last playing audio too. That made it so good being only on for internal speakers as I preferred and would change settings mode automatically when you stopped audio and started in another app.
Custom ROMs with Dolby ports doesn't remember states, however with a bit of compromise it can be used as such on this N Dolby if you prefer Dolby to only affect internal speakers. The trick is to set no extra filters and EQ in Dolby but just have Dolby enabled. With all other settings off, it still positively affects speaker audio but has no affect on headphone jack audio, you can test this by listening either way while switching on and off. This works combined with the V4A equaliser settings as previously explained. Set rather simply as so, the speaker output has less harsh treble and increased bass to sound similar in presentation to listening on quality headphones.
Extra notes
A shortcoming bug with this N Dolby port however is the Surround Virtualisation feature doesn't work on speakers. It seems reversed and only works when plugged in, I find it best to leave it off as preferred and it will stay off. This bug is unfortunate as the surround was always nice in my opinion, but it's only one loss compared to all the other gains. For what it's worth I couldn't audibly hear a benefit of the surround feature on the O port in my limited testing. Also consider if using the O port where the effects are all somewhat changed for worse in my opinion, it also has to be manually switched off afterwards to not affect plugged audio unlike with the workaround available in the N port. In terms of comparing missing new features, the Oreo version has a bass boost toggle and a dynamic setting, overall though I couldn't settle on an audio setup I liked with any Oreo Dolby settings.
Conclusion
I hope my experience will help others to finally get the most out of their speakers with Dolby and V4A. Since moving from stock N to custom Oreo in early April left me disappointed in O Dolby quality usage issues, I'd stopped using it and relied only on V4A's Speaker Optimisation setting for improving the speakers as a compromise but it always left me wanting in comparison. However now recently finally figuring all this out, i'll be using this for the forseeable future. I really adore the loud unbeatable quality Dolby speaker output for general listening, I mean even a dozen meters away it sounds transformed like a good dedicated mini speaker is playing. This coming from someone who appreciates listening on premium headphones too.
Nice work ofcourse but i dont agree nougat dolby sounds better. In dolby oreo there is more to adjust also
Predatorhaze said:
Nice work ofcourse but i dont agree nougat dolby sounds better. In dolby oreo there is more to adjust also
Click to expand...
Click to collapse
It depends on your ears (or beliefs) I guess. Regardless if you've preference for O or N's Dolby, there's still good reason to use the N port. Mainly that it's able to be set and forget and also it's working with V4A aiding it too without issue.
So after reading your guide I liked the idea of a "set and forget" approach and chose certain presets for fireequalizer while in headset (bass booster) or speaker (small speakers) modes; also I changed v4a to the older version since I was unaware of its "super driver". However in the Dolby app I chose to leave on the "intelligent eq open" because to my ears the sound came across "fuller" if that makes sense.
roisuke said:
So after reading your guide I liked the idea of a "set and forget" approach and chose certain presets for fireequalizer while in headset (bass booster) or speaker (small speakers) modes; also I changed v4a to the older version since I was unaware of its "super driver". However in the Dolby app I chose to leave on the "intelligent eq open" because to my ears the sound came across "fuller" if that makes sense.
Click to expand...
Click to collapse
I'd recommend Dolby's extra customisations to be off because they remain active when plugged in. Unless of course you like any of its setting for both plugged and speaker. Relying on V4A for separated audio modifications fits well, you could try playing around trying to improve settings there if desired.
I used to prefer Rich in Dolby with Small Speakers in V4A together with Surround Virtualisation. Now with SV unavailable, I assume the EQ effects in Dolby are less pronounced because I can't notice much of positive difference with them on. When the issue being the setting will affect plugged too, it's a small worthwhile loss turning them off for the automated convenience.
Your headset preferences will totally depend on your headphone hardware and listening preferences. From my reading and understanding it's better to only use an EQ to reduce Frequency Response range positive peaks. Never to increase EQ as that introduces artificial noise. I'll attach two screenshots showing my hifi headphones FR graph and the V4A EQ I use to show what I mean (EQ graph doesn't match scale, zoom in to see the tiny DPI X Y values). The green line is the ideal neutral target FR with bass effect for headphones. Note when adjusting V4A's graphic equaliser the range of each frequency band is only shown on the old original 2.3.4.0 version.
Obviously mobile speakers are different in severely lacking bass, accuracy and need the bass EQ boost regardless of accuracy.
Sent from my ZTE Axon 7 using XDA Labs
@roisuke, It works as expected using Magisk 16.7. I did in another order and it also worked:
1. V2A FX 1.6.9 or later (I've tested old and current versions)
2. Sauron MK II.II 02.05.2018 or later (I've tested old and current versions)
3. BQ-E4 Dolby ATMOS (Dolby-Oreo.zip)
4. AML 1.7 or later (I've tested old and current versions).
I've noticed the flashing order is irrelevant as long as AML is the last one (It is intented to be always the last module to gather all the audio configs). It works with any install option of V2A (I prefer 2.5.0.5 traditional interface).
I believe the flashing of the ARISE module reroutes the audio paths and disables the hifi DAC when the BQ-E4 Dolby ATMOS is installed. I suspect it because the quality is vastly improved only if, at the end, I flash the Mixer_AK4490.zip to restore the HiFi DAC wiring paths.
These are great news since in Oreo I haven't found a way to have DA and V4A together.
Oki said:
It works with any install option of V2A (I prefer 2.5.0.5 traditional interface).
I believe the flashing of the ARISE module reroutes the audio paths and disables the hifi DAC when the BQ-E4 Dolby ATMOS is installed. I suspect it because the quality is vastly improved only if, at the end, I flash the Mixer_AK4490.zip to restore the HiFi DAC wiring paths.
These are great news since in Oreo I haven't found a way to have DA and V4A together.
Click to expand...
Click to collapse
I already listed why I prefer 2.3.4.0. I didn't mention in general UI the newer versions hide settings behind presses, makes it harder to use and see for example the selected EQ visual profile.
I was focused on speakers so actually hadn't tested jacked audio expecting it to just continue hifi as always on newer bootstacks. I thought Ainur Sauron is supposed to include the DAC patch as @Skrem339 added Axon 7 mods to it, he's also the author of the AK4490 DAC patch in question.
In any case I gave jacked audio some testing. I immediately found with the DAC patch there's static noise when booting jacked in and charging, but it phased out after replugging power, further testing for this may be necessary. After a few short install uninstall tests audio comparison, quality does sound improved. Thanks for mentioning that detail.
Here's the DAC patch thread with system and systemless. I updated the OP with this detail. Systemless only installs through TWRP still by the way. Small note worth mentioning though maybe unrelated is my fingerprint sensor stopped working after installing the Magisk patch, but worked again after uninstalling and reinstalling (a reset may have been enough).
Infy_AsiX said:
I already listed why I prefer 2.3.4.0. I didn't mention in general UI the newer versions hide settings behind presses, makes it harder to use and see for example the selected EQ visual profile.
I was focused on speakers so actually hadn't tested jacked audio expecting it to just continue hifi as always on newer bootstacks. I thought Ainur Sauron is supposed to include the DAC patch as @Skrem339 added Axon 7 mods to it, he's also the author of the AK4490 DAC patch in question.
In any case I gave jacked audio some testing. I immediately found with the DAC patch there's static noise when booting jacked in and charging, but it phased out after replugging power, further testing for this may be necessary. After a few short install uninstall tests audio comparison, quality does sound improved. Thanks for mentioning that detail.
Here's the DAC patch thread with system and systemless. I updated the OP with this detail. Systemless only installs through TWRP still by the way. Small note worth mentioning though maybe unrelated is my fingerprint sensor stopped working after installing the Magisk patch, but worked again after uninstalling and reinstalling (a reset may have been enough).
Click to expand...
Click to collapse
This patch is useless for Roms based on Android 8 because DAC works on them without patch. Also, this DAC patch was remove from Ainur by my request to Ultra8
Skrem339 said:
This patch is useless for Roms based on Android 8 because DAC works on them without patch. Also, this DAC patch was remove from Ainur by my request to Ultra8
Click to expand...
Click to collapse
For some reason the DAC patch is required after installing the Dolby Atmos patch mentioned in the OP, even in Oreo ROMs.
Hi @Infy_AsiX, can you give a link to the exact Nougat dolby port module which you are using on Oreo together with the 2.3.4.0 v4a? I tried all Oreo versions but they give me bootloop on S8 device, thanks
paradoxxman said:
Hi @Infy_AsiX, can you give a link to the exact Nougat dolby port module which you are using on Oreo together with the 2.3.4.0 v4a? I tried all Oreo versions but they give me bootloop on S8 device, thanks
Click to expand...
Click to collapse
Following the installation links brings you to Pixel 2 XL guide with the download. But here's a link to that Pixel2XL guide anyway https://forum.xda-developers.com/pixel-2-xl/how-to/viper-dd-atom-t3724096
Sent from my ZTE Axon 7 using XDA Labs
Great [emoji3] works fine on Havoc Treble Oreo
Oki said:
For some reason the DAC patch is required after installing the Dolby Atmos patch mentioned in the OP, even in Oreo ROMs.
Click to expand...
Click to collapse
did you made Dolby working on treble ROM ? (I m on latest Havoc) because I've followed the OP (not the patch that did not install) but Dolby app quit, w/o message, after 1s. Just the nice logo
dwnoel said:
did you made Dolby working on treble ROM ? (I m on latest Havoc) because I've followed the OP (not the patch that did not install) but Dolby app quit, w/o message, after 1s. Just the nice logo
Click to expand...
Click to collapse
Well, I havent tried it in a Treble ROM. I don't play games or watch ATMOS movies. For Youtube, music and general audio, Viper4Android provides more features and richness to the sound so I don't use ATMOS at all. For external speakers I only notice more volume and some equalization, and I also have that configured in V4A in the speakers section. Treble roms are tricky. V4A is awesome when used properly.
Oki said:
Well, I havent tried it in a Treble ROM. I don't play games or watch ATMOS movies. For Youtube, music and general audio, Viper4Android provides more features and richness to the sound so I don't use ATMOS at all. For external speakers I only notice more volume and some equalization, and I also have that configured in V4A in the speakers section. Treble roms are tricky. V4A is awesome when used properly.
Click to expand...
Click to collapse
Do you mind sharing your settings? I used Atmos on dynamic setting in my car with Android Auto and Spotify. Car never sounded better. I'm now on treble with PixelExperience P and stuck with Viper. Sounds ok, but the dynamic system makes the sound go in and out.
kyuza said:
Do you mind sharing your settings? I used Atmos on dynamic setting in my car with Android Auto and Spotify. Car never sounded better. I'm now on treble with PixelExperience P and stuck with Viper. Sounds ok, but the dynamic system makes the sound go in and out.
Click to expand...
Click to collapse
I use V4A 2.5.0.5 with the classic interface with these settings:
Master Pwr ON
Playback Gain Control: ON
Extreme
4x
-1.9 dB
Spectrum Extension: ON
0.37
Dynamic System: ON
Common Earphone v2
25%
Viper Clarity: ON
Natural
6.0 dB
The rest is off, even the EQ
Been meaning to ask, @Oki. Your settings above are for headphones, right?
The Axon 7 isn't my daily driver so I don't use headphones with it much as I don't carry it around. Been trying to get some good speaker settings, mostly for locally stored music and occasional streaming video.
On this Nougat ROM Dolby Atmos and Viper 2.6.0.5 are working well together. In AEX 5.4 Oreo the two are also working but not necessarily together. A long time ago someone posted custom FireEQ settings which I still use but the other stuff not too sure about.
ZTE Axon 7 A2017U, Dark ROM, LlamaSweet 0.5 Kernel, Multiboot, XDA Legacy
Has anyone got Dolby to work on LOS 15.1?
EDIT: Never mind, got it working by going to the pixel 2xl forum for it
troy5890 said:
Has anyone got Dolby to work on LOS 15.1?
EDIT: Never mind, got it working by going to the pixel 2xl forum for it
Click to expand...
Click to collapse
Are you on the latest nightly los 15.1? Dolby just crashes for me now on latest
roisuke said:
Are you on the latest nightly los 15.1? Dolby just crashes for me now on latest
Click to expand...
Click to collapse
I'm on the latest LOS official 15.1 . I used the zip called "Dolby-Oreo.zip" the one for BQ.

No LDAC with MDR-1000X?

Hi everyone,
I noticed on my Pocophone that I only get aptx in dev settings, and while LDAC shows up as an option, it gives me a slide crack noise when selecting it, and keeps going back to aptx (at least it says so in the Settings).
Anyone experience similiar issues or found a solution?
Anyone? Can someone confirm that LDAC works just fine for them?
No it doesn't work at all, it seems they didn't implement support for LDAC at all! Tested with Sony MDR XB80 BS and 1MORE E1001BT
Did you try it on MIUI 10 Beta? As far as I know, they only impelemented it on Oreo based MIUI 10 though I can't test since I don't have LDAC headphones

No sound when using LDAC

I have read the the device is support LDAC Bluetooth.
But when I change Bluetooth codec in developer setting to LDAC it got no sound. Testing with my fiio btr3 the indicator light change to white thae mean I using LDAC but got no sound.
The only codec that work is just sbc, aac and aptx.
Anyone know how to enable LDAC or just tell me that it not supported LDAC yet.
PS. When using the other codec it has worst quality than it should tho compare to my Nokia8. Why this happen?
sadin911 said:
I have read the the device is support LDAC Bluetooth.
But when I change Bluetooth codec in developer setting to LDAC it got no sound. Testing with my fiio btr3 the indicator light change to white thae mean I using LDAC but got no sound.
The only codec that work is just sbc, aac and aptx.
Anyone know how to enable LDAC or just tell me that it not supported LDAC yet.
PS. When using the other codec it has worst quality than it should tho compare to my Nokia8. Why this happen?
Click to expand...
Click to collapse
Bluetooth speaker/device should support also LDAC. Not only the Smartphone that have a LDAC capability
philipjan26 said:
Bluetooth speaker/device should support also LDAC. Not only the Smartphone that have a LDAC capability
Click to expand...
Click to collapse
i have the same issue. I have Sony wh-1000xm3 headphones. When i switched the LDAC codec. Sound just gone. Is anyone found a solution for this?
I search for it and found the samsung s9 s8 etc. phones have similar kind of problem. They have a solution for this. They just turn off the "dual audio" feature. But i cant find that setting in A3.
kaelthasxx said:
i have the same issue. I have Sony wh-1000xm3 headphones. When i switched the LDAC codec. Sound just gone. Is anyone found a solution for this?
I search for it and found the samsung s9 s8 etc. phones have similar kind of problem. They have a solution for this. They just turn off the "dual audio" feature. But i cant find that setting in A3.
Click to expand...
Click to collapse
Same thing, @kaelthasxx. I'm also trying to setup my wh1000xm3 with the Mi A3 and there's just no way of making ldac work. Not to mention that using aptx gets me an awful quality. If I run a frequency response test I get a lot of crackling at frequencies around 17-20khz with aptx.
The best quality I managed to get out of this setup was using sbc, which is a shame since the headphones support all the way up to ldac.
I think this is some issue with the OS (I'm using the phone's native Android One), since in theory the BT soc of this phone should support these technologies. Hope they fix it for Android 10.
I had install custom rom and it work just fine. Can't wait for official release tho
Sent from my MI A3 using Tapatalk
sadin911 said:
I had install custom rom and it work just fine. Can't wait for official release tho
Sent from my MI A3 using Tapatalk
Click to expand...
Click to collapse
What ROM are you using? The official one doesn't even support aptx properly (I get a lot of distortion using it with Sony's WH-1000xm3). Not sure if I should flash a custom ROM or pray for a fix in Android 10.
Anyone have a solution for this, just got some Sony Bluetooth cans for xmas and bow have same issue...
Is it confirmed fixed in Android 10 (ie a month or so factory fix all going well) or should I just go custom rom and fix it now (although the whole reason I went a3 was to get a stock Android device)
If I was to go rom route what's the suggested rom? I'm assuming a3 and a3 lite use the same base rom package?
Thanks to all in advance
G.
does anyone know if this problem has been solved with android 10?
sitolupion said:
does anyone know if this problem has been solved with android 10?
Click to expand...
Click to collapse
I can't confirm for LDAC, but AAC doesn't work, it always revert to sbc. For now is better to try a custom as bluetooth codecs never worked for me.
here you go! was also waiting for long months to access any better then SBC...
A3 with A10 stock, April version + Sony XM3, latest app version
--> AptX is on!
checked developer settings and this confirms. AptX is shown on (its not AptX HD by the way). trying to select any better eg LDAC wont stick when return from setting, also no codec effect.
at least something... good luck guys!
No
sitolupion said:
does anyone know if this problem has been solved with android 10?
Click to expand...
Click to collapse
No
Any update on this? How does the phone do with the latest firmwares?
(I plan to get Sony headphones)
Mi A3 with Android 11 here. No LDAC option, best is aptX but the WH-1000-XM4 dont support it so... best codec is AAC.

Categories

Resources