I want to use my Mi6 on my car radio (Pioneer MVH-S300BT) by connecting via bluetooth. The connection is successful, but the bluetooth audio codec that the phone selects by default (AAC) doesn't give a sound. It only works when I go into the developer options and select the SBC codec by hand. This is annoying, since I need to follow all the steps everytime I want to connect both devices (it always starts the default AAC). I was wonderig if it is possibe to change some setting so the phone stays perminentsly on the SBC instead of going back to the AAC codec with every new connection?
I found this on a forum about changing the priority use of bluetooth audio codec, and ik comes close to what I am looking for:
Devices running Android 8.0 that support A2DP automatically gain the additional codec support. Device manufacturers may need to obtain separate licenses and binary blobs for some proprietary audio codecs. In addition to SBC, Android 8.0 supports the following codecs:
AAC
aptX
aptX HD
LDAC
Device manufacturers can choose which codecs their devices attempt to use first. Set the codec priorities by changing the following values in the file res/values/config.xml:
<!-- Configuring priorities of A2DP source codecs. Larger value means
higher priority. Value -1 means the codec is disabled.
Value 0 is reserved and should not be used here. Enabled codecs
should have priorities in the interval [1, 999999], and each
priority value should be unique. -->
<integer name="a2dp_source_codec_priority_sbc">1001</integer>
<integer name="a2dp_source_codec_priority_aac">2001</integer>
<integer name="a2dp_source_codec_priority_aptx">3001</integer>
<integer name="a2dp_source_codec_priority_aptx_hd">4001</integer>
<integer name="a2dp_source_codec_priority_ldac">5001</integer>
However, I could not apply this option since I was unable to find the file having these settings.
Therefore I hope someone here on the forum can help me finding the solution
I came across the exact same problem and after investigated for a while I came up with a fairly easy workaround.
TLDR: You need root, edit your build.prop (using text editor, some app from the play store, etc) and change the following key: persist.vendor.bt.a2dp_offload_cap
by removing -aac from the string.
for example my value was: persist.bt.a2dp_offload_cap=sbc-aptx-aptxhd-aac
and now it has: persist.bt.a2dp_offload_cap=sbc-aptx-aptxhd
That should be enough to make sure it defaults to sbc when connecting BT to an AAC enabled decide (such as the pioneer radios) and with no need to change the developer options with each connection.
Long story: so apparently mi6 got screwed a bit in android 8 oreo. my guess is that either AAC lib is missing or corrupted. either way I found out that our build.prop is missing the value: qcom.hw.aac.encoder=true
and on top of that, the other hw encoder value is set to false: vendor.audio.hw.aac.encoder=false.
I tried adding and turning them both to on but I still couldn't hear music from my pioneer deh radio (deh-s4050bt).
Along the way I installed the aptx/aptx-hd codecs using magisk but that didn't help because the radio apparently doesn't support the codecs (which is also why I have them in my offload string).
eventually I decided to give up on trying to make AAC work and just disable it from the offload string by removing the '-aac' from the build.prop value: persist.vendor.bt.a2dp_offload_cap
Alternatively you can try just moving the 'aac' to the start of the stack (thinking it might work like a priority thing) so the value will look like this: persist.vendor.bt.a2dp_offload_cap=aac-sbc-aptx-aptxhd
Let me know if it also worked.
That seemed to do the trick but it does require root permission which with xiaomi is kind of hard to get, when you have to first unlock bootloader (but if someone has another method for temporarily getting root permission and editing the file then go for it).
A really good fix will probably include the correct aac lib (I suppose it needs to match our hardware a.k.a snapdragon 835) and enabling the hw.audio.aac.encoder values.
If someone can get a hold of the libraries and make a zip to run from twrp or a magisk module that will be great. I will continue to investigate hopefully to come up with a better solution before xiaomi will release the fix.
I myself running the latest beta/developer global miui rom with unlocked bootloader and magisk on a xiaomi mi6 6/128. It will be great if people running different roms such as lineageos will report about their experience and maybe provide us with their build.prop or corresponding libraries.
Cheers
rtk217 said:
I came across the exact same problem and after investigated for a while I came up with a fairly easy workaround.
TLDR: You need root, edit your build.prop (using text editor, some app from the play store, etc) and change the following key: persist.vendor.bt.a2dp_offload_cap
by removing -aac from the string.
for example my value was: persist.bt.a2dp_offload_cap=sbc-aptx-aptxhd-aac
and now it has: persist.bt.a2dp_offload_cap=sbc-aptx-aptxhd
That should be enough to make sure it defaults to sbc when connecting BT to an AAC enabled decide (such as the pioneer radios) and with no need to change the developer options with each connection.
Long story: so apparently mi6 got screwed a bit in android 8 oreo. my guess is that either AAC lib is missing or corrupted. either way I found out that our build.prop is missing the value: qcom.hw.aac.encoder=true
and on top of that, the other hw encoder value is set to false: vendor.audio.hw.aac.encoder=false.
I tried adding and turning them both to on but I still couldn't hear music from my pioneer deh radio (deh-s4050bt).
Along the way I installed the aptx/aptx-hd codecs using magisk but that didn't help because the radio apparently doesn't support the codecs (which is also why I have them in my offload string).
eventually I decided to give up on trying to make AAC work and just disable it from the offload string by removing the '-aac' from the build.prop value: persist.vendor.bt.a2dp_offload_cap
Alternatively you can try just moving the 'aac' to the start of the stack (thinking it might work like a priority thing) so the value will look like this: persist.vendor.bt.a2dp_offload_cap=aac-sbc-aptx-aptxhd
Let me know if it also worked.
That seemed to do the trick but it does require root permission which with xiaomi is kind of hard to get, when you have to first unlock bootloader (but if someone has another method for temporarily getting root permission and editing the file then go for it).
A really good fix will probably include the correct aac lib (I suppose it needs to match our hardware a.k.a snapdragon 835) and enabling the hw.audio.aac.encoder values.
If someone can get a hold of the libraries and make a zip to run from twrp or a magisk module that will be great. I will continue to investigate hopefully to come up with a better solution before xiaomi will release the fix.
I myself running the latest beta/developer global miui rom with unlocked bootloader and magisk on a xiaomi mi6 6/128. It will be great if people running different roms such as lineageos will report about their experience and maybe provide us with their build.prop or corresponding libraries.
Cheers
Click to expand...
Click to collapse
Well. MIUI10 seems solve this issue. AAC offload is working fine and AAC itself is working fine.
I tested with my backport BT framework from MIUI10.
aarwwefdds said:
Well. MIUI10 seems solve this issue. AAC offload is working fine and AAC itself is working fine.
I tested with my backport BT framework from MIUI10.
Click to expand...
Click to collapse
Where did you get MIUI 10 for mi6? and can you share your framework?
rtk217 said:
Where did you get MIUI 10 for mi6?
Click to expand...
Click to collapse
I'm using MIX2, not MI6. They're sharing same BT hardware and both are based on 835.
I've made a Magisk module. Maybe you can test it on MI6 and see if it is work or not, if you want.
https://forum.xda-developers.com/showthread.php?t=3799806
rtk217 said:
I came across the exact same problem and after investigated for a while I came up with a fairly easy workaround.
TLDR: You need root, edit your build.prop (using text editor, some app from the play store, etc) and change the following key: persist.vendor.bt.a2dp_offload_cap
by removing -aac from the string.
for example my value was: persist.bt.a2dp_offload_cap=sbc-aptx-aptxhd-aac
and now it has: persist.bt.a2dp_offload_cap=sbc-aptx-aptxhd
That should be enough to make sure it defaults to sbc when connecting BT to an AAC enabled decide (such as the pioneer radios) and with no need to change the developer options with each connection.
Long story: so apparently mi6 got screwed a bit in android 8 oreo. my guess is that either AAC lib is missing or corrupted. either way I found out that our build.prop is missing the value: qcom.hw.aac.encoder=true
and on top of that, the other hw encoder value is set to false: vendor.audio.hw.aac.encoder=false.
I tried adding and turning them both to on but I still couldn't hear music from my pioneer deh radio (deh-s4050bt).
Along the way I installed the aptx/aptx-hd codecs using magisk but that didn't help because the radio apparently doesn't support the codecs (which is also why I have them in my offload string).
eventually I decided to give up on trying to make AAC work and just disable it from the offload string by removing the '-aac' from the build.prop value: persist.vendor.bt.a2dp_offload_cap
Alternatively you can try just moving the 'aac' to the start of the stack (thinking it might work like a priority thing) so the value will look like this: persist.vendor.bt.a2dp_offload_cap=aac-sbc-aptx-aptxhd
Let me know if it also worked.
That seemed to do the trick but it does require root permission which with xiaomi is kind of hard to get, when you have to first unlock bootloader (but if someone has another method for temporarily getting root permission and editing the file then go for it).
A really good fix will probably include the correct aac lib (I suppose it needs to match our hardware a.k.a snapdragon 835) and enabling the hw.audio.aac.encoder values.
If someone can get a hold of the libraries and make a zip to run from twrp or a magisk module that will be great. I will continue to investigate hopefully to come up with a better solution before xiaomi will release the fix.
I myself running the latest beta/developer global miui rom with unlocked bootloader and magisk on a xiaomi mi6 6/128. It will be great if people running different roms such as lineageos will report about their experience and maybe provide us with their build.prop or corresponding libraries.
Cheers
Click to expand...
Click to collapse
This is just what I needed, it works! Great and thank you very, very much for this simple solution for such a persistent problem.
aarwwefdds said:
I'm using MIX2, not MI6. They're sharing same BT hardware and both are based on 835.
I've made a Magisk module. Maybe you can test it on MI6 and see if it is work or not, if you want.
https://forum.xda-developers.com/showthread.php?t=3799806
Click to expand...
Click to collapse
I took you magisk module and tweaked it just a bit and it works for mi6, to my surprise it decided to use SBC with my pioneer deh radio instead of AAC (as it insisted before) might have something to do with the interop_database.conf, I'll go over the changes between the files and try to pin point the issue.
I couldn't verify ldac as I have no device supporting it.
rtk217 said:
I took you magisk module and tweaked it just a bit and it works for mi6, to my surprise it decided to use SBC with my pioneer deh radio instead of AAC (as it insisted before) might have something to do with the interop_database.conf, I'll go over the changes between the files and try to pin point the issue.
I couldn't verify ldac as I have no device supporting it.
Click to expand...
Click to collapse
Have you revert your change of the props? If you change the prop and delete the "aac" from the offload then AAC will be disabled.
If after you revert the changes the AAC still not working, you can upload your logcat log. Make sure you get the log as soon as the pairing finish.
Any solution?
The file is no longer.
astur_82 said:
Any solution?
The file is no longer.
Click to expand...
Click to collapse
i had this problem too. in miui 9 after updating to miui 10 the problem is gone.
Download the latest firmware to your pioneer:
pioneer-car_eu/_eur_/products_/mvh-s300bt_/support
Sorry, fix the link, i cant post.
For me is working fine.
tpaulussen said:
I want to use my Mi6 on my car radio (Pioneer MVH-S300BT) by connecting via bluetooth. The connection is successful, but the bluetooth audio codec that the phone selects by default (AAC) doesn't give a sound. It only works when I go into the developer options and select the SBC codec by hand. This is annoying, since I need to follow all the steps everytime I want to connect both devices (it always starts the default AAC). I was wonderig if it is possibe to change some setting so the phone stays perminentsly on the SBC instead of going back to the AAC codec with every new connection?
I found this on a forum about changing the priority use of bluetooth audio codec, and ik comes close to what I am looking for:
Devices running Android 8.0 that support A2DP automatically gain the additional codec support. Device manufacturers may need to obtain separate licenses and binary blobs for some proprietary audio codecs. In addition to SBC, Android 8.0 supports the following codecs:
AAC
aptX
aptX HD
LDAC
Device manufacturers can choose which codecs their devices attempt to use first. Set the codec priorities by changing the following values in the file res/values/config.xml:
<!-- Configuring priorities of A2DP source codecs. Larger value means
higher priority. Value -1 means the codec is disabled.
Value 0 is reserved and should not be used here. Enabled codecs
should have priorities in the interval [1, 999999], and each
priority value should be unique. -->
<integer name="a2dp_source_codec_priority_sbc">1001</integer>
<integer name="a2dp_source_codec_priority_aac">2001</integer>
<integer name="a2dp_source_codec_priority_aptx">3001</integer>
<integer name="a2dp_source_codec_priority_aptx_hd">4001</integer>
<integer name="a2dp_source_codec_priority_ldac">5001</integer>
However, I could not apply this option since I was unable to find the file having these settings.
Therefore I hope someone here on the forum can help me finding the solution
Click to expand...
Click to collapse
does anyone have copies of the AAC codec? i have all the build.prop entries but the aac codec is missing
So far I have not seen any Nougat ROMs including the library meant for aptX support. I tried to manually place the library (libbt-aptx-x86-4.x.x.so, like the one from ARISE), but it doesn't work as my aptX-capable headset is still choosing SBC, implying the actual support of such is more than just a library. As SBC introduces a ~500ms latency, for my use cases (including but not limited to videos and rhythm games) it's completely unacceptable.
On the other hand, is aptX working with stock MM based ROMs? Apparently the device is in the official supported devices list, so I assume that might be the case. But anyway, is it possible to include aptX on recent Nougat ROMs?
Installing ARISE appears to be a no-go for this device as while it includes aptX-related libraries, it doesn't magically enable aptX and instead breaks all sensors.
EDIT: It seems most ROMs still use Bluedroid, and for that it seems the x86 aptX libs alone won't be enough. I did confirm that my headset (EP725) does support aptX on my Pixel C (currently running Oreo, though the aptX Magisk module for Oreo is required for it to actually work).
EDIT 2: A late update... apparently, the latency is not that much different with aptX, and it turned out to be more a problem with Unity than with the bluetooth codec itself after searching for a bit further... so I was wrong about aptX anyway...
Bump on this thread.
I found the libs here which seems to have been taken from stock MM ROM. But obviously just replacing libbluetooth_jni.so from TWRP with that one would only lead to crashes as there's probably some additional work needed (maybe recompile the Bluetooth apk)...
Unfortunately most of that thread is about how to get it working on ARM based smartphones and/or on Oreo (which our phone doesn't have yet, and most likely the Magisk modules and such are as well ARM-only). The post I referenced is the only one that's at least helpful to some extent, after some basic searching.
EDIT: If all isn't going to work then I have no choice but to look for ways to downsample system audio output to 8-11kHz (or maybe 8-bit) to mitigate the latency... since the usage involved is already lossy with low bitrate, I don't think downsampling would cause any unacceptable loss of quality anyway.
EDIT 2: The libs alone definitely aren't enough. Tried replacing the libs in both /system/lib/ and /system/app/Bluetooth/lib/x86/ and it still crashed when opening.
I've researched on the web for quite some time on this topic but didn't find anything definitive yet (a clear answer if it works - how to set up, etc.):
some are mentioning that only the right app would be needed to be used (well, no)
a few are mentioning that there is supposed to be an app that toggles between default dac (wcd934x) and quad dac (es9218p)
others are referring to a setting in build.prop (nope, the ROM doesn't have the mechanisms to react to that - and neither do the drivers most likely - or at least we need to make sure that this stuff is included for us)
then there are a few mentioned cases that there's support on lineageOS on board to utilize the es9218*
there's also occurences where it's mentioned that the sound stops working entirely when switching tracks (?!) - so it's still WIP
so at least the kernel needs to be set up that way - but there's probably more to it
*referencing:
https://forum.xda-developers.com/v20/development/dev-cm14-t3509953/page25 [ROM][ALL VARIANTS] LineageOS-14.1 for LG V20 [Weeklys']
https://forum.xda-developers.com/v20/development/kernel-gamma-kernel-us996-ls997-h910-t3788279/page2 [KERNEL][AOSP][AnyKernel][LOS-15.1+EAS] Gamma Kernel for [All Lineage Variants
https://forum.xda-developers.com/v2...fficial-lineageos-15-1-lg-v20-t3775689/page19 [ROM][H910|H918|LS997|US996|VS995|H990*] UNOFFICIAL LineageOS-15.1 for LG V20
https://pastebin.com/uQgyHm3b
further references:
https://forum.xda-developers.com/lg-v30/how-to/v30-quad-dac-root-bybass-fix-t3725854 V30 Quad DAC Root Bybass fix
edit:
For those who only use the quad dac for local playback (music stored on their device; NO Youtube, Streaming, etc. with Quad DAC on LineageOS/AEX/RR for now) - there is an app (for purchase) that activates & uses the quad dac (es9218p)
I've tested it and got the same specific quirk / behavior I got on LG Stock ROM with activated quad dac option.
The app is not cheap (6.99 EUR, >8 USD) - but it's totally worth it, the UI is great, the sound output is awesome (finally quad dac on non-stock !) and it uses a "custom developed USB audio driver"
extreamsd said:
This bypasses the Android audio system completely, meaning that Android's limitations regarding bit resolution and sample rate (16-bit/48kHz) are made irrelevant and high quality audio streams are fed directly to the DAC, making playback up to 32-bit at 384kHz possible (depending on the DAC capabilities) or even DSD.
Click to expand...
Click to collapse
Source: http://www.extreamsd.com/index.php/products/usb-audio-player-pro
GooglePlay link: https://play.google.com/store/apps/details?id=com.extreamsd.usbaudioplayerpro
zacharias.maladroit said:
Well, it's not fully "solved" - since only locally played content (no videos ! no streaming !),
but at least local content is played through the quad dac (es9218p).
So thank you very much for that hint (and everyone else who kept on mentioning it)
And: YES, the quad dac definitely is being used with USB Audio Player PRO
First I thought that the more punchy sound output could be placebo/imagination (with Xiaomi Piston V2 & the B & O Play Headphones),
but then I plugged in the Xiami Hybrid Pro (these are the only headphones that don't work with the quad dac for me - since they cause a extreme loud hissing/static on the left channel),
and after a few seconds I got the characteristic hissing on the left channel - that means that the es9218p DAC/sound card/AMP is definitely being used
That's the same behavior I got on LG Stock ROM after enabling the quad dac
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=77233521&postcount=209
In theory we would just need to write a HAL or something like that, which interacts with the kernel driver, its already there, just something needs to talk to it.
And some Overlay in the Settings to enable/disable the HAL.
The HAL would be C/++ while the Settings overlay would then be Java .... I could do the later.
SGCMarkus said:
In theory we would just need to write a HAL or something like that, which interacts with the kernel driver, its already there, just something needs to talk to it.
And some Overlay in the Settings to enable/disable the HAL.
The HAL would be C/++ while the Settings overlay would then be Java .... I could do the later.
Click to expand...
Click to collapse
I don't really have the programming skills to do either, but I'll buy you guys a beer if you figure it out. That and the vibration motor issues are the only reason I'm still on a stock ROM.
MaxusValtron said:
I don't really have the programming skills to do either, but I'll buy you guys a beer if you figure it out. That and the vibration motor issues are the only reason I'm still on a stock ROM.
Click to expand...
Click to collapse
Vibration motor issues may be solved. Dev is currently trying user @Krakophyst suggestion to replace vibration motor files with those from V35. Now why that would work better than actual V30 files, don't know. But it worked for the user.
Krakophyst said:
The vibration problem came up, but I think I fixed it by replacing vibration related files in /vendor and its subfolders with LG V35's files and it has been working fine for about three days now.
Click to expand...
Click to collapse
ChazzMatt said:
Vibration motor issues may be solved. Dev is currently trying user suggestion to replace vibration motor files with those from V35. Now why that would work better than actual V30 files, don't know. But it worked for the user.
Click to expand...
Click to collapse
It works, because the V35 files have to work on AOSP (because of treble implementation on the V35), while ours depend heavily on the LG framework (which probably does its own stuff to the vibration services), and arent supposed to ever run on AOSP.
SGCMarkus said:
It works, because the V35 files have to work on AOSP (because of treble implementation on the V35), while ours depend heavily on the LG framework (which probably does its own stuff to the vibration services), and arent supposed to ever run on AOSP.
Click to expand...
Click to collapse
Aha. Then score one for Treble on an LG phone that has some similar features to ours. V35 may never get bootloader unlock and root, but we can cannibalize it for the V30.
SGCMarkus said:
It works, because the V35 files have to work on AOSP (because of treble implementation on the V35), while ours depend heavily on the LG framework (which probably does its own stuff to the vibration services), and arent supposed to ever run on AOSP.
Click to expand...
Click to collapse
Wait!?!? So could volte possibly work with the v35 files???
suzook said:
Wait!?!? So could volte possibly work with the v35 files???
Click to expand...
Click to collapse
IF (a big if) volte works on GSIs (which nobody tried so far from what i know, i only know 1 person with a G7, and he cant use VoLTE, thanks to the carrier), those files are highly device specific (or atleast SoC specific), its very unlikely that those would work for us.
I could try, but dont get your hopes up on that.
SGCMarkus said:
IF (a big if) volte works on GSIs (which nobody tried so far from what i know, i only know 1 person with a G7, and he cant use VoLTE, thanks to the carrier), those files are highly device specific (or atleast SoC specific), its very unlikely that those would work for us.
I could try, but dont get your hopes up on that.
Click to expand...
Click to collapse
One can dream though! Lol. Of you need me to test, let me know. Thanks!
Added: USB Audio Player PRO to the first post
and practical proof/experience that it utilizes the quad dac on non-Stock ROMs (AEX, AOSP Extended as example)
PlayStore Link:
https://play.google.com/store/apps/details?id=com.extreamsd.usbaudioplayerpro
zacharias.maladroit said:
Added: USB Audio Player PRO to the first post
and practical proof/experience that it utilizes the quad dac on non-Stock ROMs (AEX, AOSP Extended as example)
PlayStore Link:
https://play.google.com/store/apps/details?id=com.extreamsd.usbaudioplayerpro
Click to expand...
Click to collapse
I grabbed the app, it had some Network options (notably for Tidal and Google Play Music) I would assume using those options from within the app would use the DAC? Can't test personally as I'm currently using Spotify but would happily switch if I could use the DAC on a streaming service, assuming at least ~80% songs I have on Spotify are available there.
zomgalama said:
I grabbed the app, it had some Network options (notably for Tidal and Google Play Music) I would assume using those options from within the app would use the DAC? Can't test personally as I'm currently using Spotify but would happily switch if I could use the DAC on a streaming service, assuming at least ~80% songs I have on Spotify are available there.
Click to expand...
Click to collapse
Could very well be that it provides or uses hooks to interact with those and I guess it should work (if it works, if it doesn't you can nag the devs to fix it - it's a somewhat "premium" priced app after all, and support is to be expected )
I'm not using any streaming services, sorry - so can't test.
Pretty sure there must be users of Spotify here around so maybe those can give some feedback
Edit: mistyped
Anyways I started a Tidal subscription (hifi student plan). From listening to a couple songs things definitely seem clearer but can't say for sure if it's using the DAC or placebo/better quality audio is the cause.
zacharias.maladroit said:
Could very well be that it provides or uses hooks to interact with those and I guess it should work (if it works, if it doesn't you can nag the devs to fix it - it's a somewhat "premium" priced app after all, and support is to be expected )
I'm not using any streaming services, sorry - so can't test.
Pretty sure there must be users of Spotify here around so maybe those can give some feedback
Click to expand...
Click to collapse
I probably will be switching off Spotify in favor of this; only because the student plan for it exists and I do hear an audible difference with their hifi settings ($19.99/month for hifi plan without a student discount yeeesh).
even using this app on non stock rom can we still get the same high volume output from the stock rom with HIM sound mod?
Sent from my LG-H930 using Tapatalk
chalmizzle said:
Anyone tried the Onkyo HF Player app?
Click to expand...
Click to collapse
just tried it with the Xiaomi Pro HD Hybrid and I get the characteristic strong hissing noise in one of the channels (left channel) - that's the only headphones I get that weird thing with when the quad dac is activated (on stock ROM).
This confirms that the es9218p ("quad dac") also works with Onkyo HF Player on non-Stock :good:
So obviously these applications HF player and USB audio pro player have some line of code that is triggering the quad DAC to be utilized. Correct?
u4icpain said:
So obviously these applications HF player and USB audio pro player have some line of code that is triggering the quad DAC to be utilized. Correct?
Click to expand...
Click to collapse
And one also works with streaming media.
zacharias.maladroit said:
Added: USB Audio Player PRO to the first post
and practical proof/experience that it utilizes the quad dac on non-Stock ROMs (AEX, AOSP Extended as example)
PlayStore Link:
https://play.google.com/store/apps/details?id=com.extreamsd.usbaudioplayerpro
Click to expand...
Click to collapse
Would you still need to use higher ohm headphones to enable the quad DAC , or will this (USB Player Pro) allow any headphones to work with it?
I've got 4 sets of IEMs that I love, and would hate to have to start all over again buying new ones.
christoophat said:
Would you still need to use higher ohm headphones to enable the quad DAC , or will this (USB Player Pro) allow any headphones to work with it?
I've got 4 sets of IEMs that I love, and would hate to have to start all over again buying new ones.
Click to expand...
Click to collapse
Nope, I'm using the quad/dedicated DAC with "normal", low ohm/impedance headphones myself,
the only "difference" is that there isn't much noticeable difference compared to the default (qualcomm) audio DAC
So you'll be fine,
you can choose to get yourself higher ohm headphones in the future (after careful evaluation, of course) take your time to choose the ones that best fit your hearing preferences (sound response, etc.)
Any updates on getting the dac to work with non stock roms?
Hey,
I'm currently looking for a smartphone with long battery life and support of HQ sound (LDAC preferred).
I found some ROMs with Android 8.0 and I heard that this version of OS supports LDAC. Does it mean that when I install one of these ROMs, I will be able to use LDAC?
Koprzywa said:
Hey,
I'm currently looking for a smartphone with long battery life and support of HQ sound (LDAC preferred).
I found some ROMs with Android 8.0 and I heard that this version of OS supports LDAC. Does it mean that when I install one of these ROMs, I will be able to use LDAC?
Click to expand...
Click to collapse
LDAC is included in AOSP since Oreo so you should be able to use it on every 8+ ROM until someone will remove it from his ROM. It is visible in my codec selection menu on LOS15.1 but I can't test it for you since I'm not in possession of any wireless headphones. I believe that you should look for information and how it works on other phones threads too, not only here. There is possibility that Lineage doesn't support this codec itself since stock haven't supported it but I'm not sure about that since LDAC is part of AOSP unlike AptX for example where your phone needs to be certified to allow developers to include this codec in official builds.
Basically you can add any existing bluetooth audio codec to your phone's ROM. There's not any hardware requirements besides bluetooth so I believe that you should be able to use it.
Hello,
I'm using my mi mix 2 with havoc os 2.9 (android 9), that allows to record AUDIO in stereo, from apps like "hi-q mp3 recorder" if you select "raw source".
As long as I know that this way, this software is using both microphones (one up, and one down) and the recordings are awesome, I want to use a camera that ALSO is able to record audio in stereo.
- Is there a Gcam mod that does that ?
- ... Or any other camera app ?
- ... Or any way to change, e.g., the file /vendor/etc/media_profiles_v1_0.xml to record in stereo ? (already tried to set channels to 2 but it didn't worked)
... And the serious and hard way: I'm a .net + Lua developer, and I'd never made custom roms, so no idea to develop an app in android or even an entire custom rom. I'm assuming that it would be very hard for me to change, debug and made a gcam mod that allows what I want, because, in other words, I don't know where to start ... I prefer a more easy solution.
- Do ALL Android phones follow the same rule to get / set audio configurations ? Is there an 'official documentation' about it ?
Ok, I'm stop asking now (at last! xd) ... Best,
Obsy