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
Related
EDIT JUNE 2018: This thread is no longer needed. If you're on the latest versions of AOSP/LOS then all you need is Magisk to install APTx and have it working.
Original thread continues below.
================================
This post will help you add aptX Bluetooth capability to your Pixel XL.
NOTE: This mod is only for ROM's using the Qualcomm Bluetooth stack, such as 14.1+ Cyanogen/Lineage OS.
Does not work in ROM's using the AOSP Bluetooth stack, such as Stock Pixel, Dirty Unicorns/Pure Nexus.
Apt-X and Apt-X HD are officially supported in Lineage OS based ROM's
https://www.xda-developers.com/late...port-for-aptx-and-aptxhd-caf-rebase-and-more/
For the moment, this thread only deals with non-HD aptX.
aptX HD is still rarely supported by headphones & other devices.
I'll research and add appropriate files for HD soon.
-------------------------------
-------------------------------
KNOWN COMPATIBLE ROMs:
CRDroid
Hexa-Project
Lineage OS
OctOS
Resurrection Remix
Tesla
Tipsy
-------------------------------
-------------------------------
DIRECTIONS TO INSTALL MOD:
Just go to this post and flash the zip in TWRP.
Please make sure to give @Namelesswonder many thanks for creating the zip for us!!!
https://forum.xda-developers.com/showpost.php?p=72267710&postcount=104
-------------------------------
-------------------------------
VERIFY MOD IS WORKING
To verify the mod is working, you should only need your ears and a HIGH QUALITY audio file.
Otherwise, you can use search your logcat for the string "aptx" to verify it's being enabled.
Such as in the output you see below.
Code:
01-14 18:57:40.539 1457 1625 I bt_btif_media: btif_a2dp_encoder_init Selected Codec [b]aptX[/b]
01-14 18:57:40.646 1457 4089 W bt_osi_thread: run_thread: thread id 4089, thread name [b]aptx[/b]_media_worke started
-------------------------------
-------------------------------
Have you heard of aptX Bluetooth?
It lets your Bluetooth connection deliver cleaner, fuller sounding audio to aptX supported devices (headphones, car stereo, etc).
Your Pandora may not sound any better, but your FLAC and other high end MP3 type files should sound cleaner, slightly more sparkly highs and better defined lows.
Think of it as the difference between listening to FM radio vs. a CD.
While it's not that drastic a difference, a capable ear should be able to enjoy what aptX delivers.
Same goes for HD voice calls if you have access to that. There may be more clarity noticed on these types of calls when using an aptX supported audio chain.
The aptX mod should not interfere with Viper or any other Android audio mod.
It's simply a codec, such as A2DP using SBC. But instead of SBC, you'll be using aptX.
Please give a big thanks to @dh.harald for coming up with this particular solution.
https://forum.xda-developers.com/oneplus-3/themes/mod-aptx-codec-t3521228
Here is my original aptX thread from 2013 containing dated discussions leading to our current status.
https://forum.xda-developers.com/showthread.php?t=2531440
Bluetooth® is limited by a maximum available bandwidth so it’s not always suitable for delivering high quality audio
Click to expand...
Click to collapse
Qualcomm aptX audio enables CD-like quality wireless audio because it solves the problem of sending the full music bandwidth over Bluetooth
Click to expand...
Click to collapse
Compression ratio: 4:1
Audio Format: 16-bit, 44.1kHz (CD-Quality)
Data Rates: 352kbps
Frequency Response: 10Hz to 22kHz
Algorithmic Delay: <1.89ms @ Fs 48KHz
Dynamic Range: 16-bit: >92dB
THD+N: -68.8dB
Click to expand...
Click to collapse
What are head-fi members views on apt-x lossless codec (over bluetooth)?
How good is bluetooth audio at its best?
-------------------------------
-------------------------------
Will this work with pure nexus ROM?
kirschdog1 said:
Will this work with pure nexus ROM?
Click to expand...
Click to collapse
Unlikely. I think they use AOSP Bluetooth stack.
You can try though, it won't break anything to put the files in the same location.
But I'm fairly sure it'll be a waste of time.
Someone with a Nexus 6 said it didn't work on their pure nexus ROM.
CZ Eddie said:
Unlikely. I think they use AOSP Bluetooth stack.
You can try though, it won't break anything to put the files in the same location.
But I'm fairly sure it'll be a waste of time.
Someone with a Nexus 6 said it didn't work on their pure nexus ROM.
Click to expand...
Click to collapse
I have it in my stock ROM, rooted with a custom kernel. I haven't tested it out yet. But I feel like these files do what I usually do manually in system/etc/a2dp_audio_policy_configuration.xml set the values to "96000,192000" and Bluetooth dramatically increases in depth and clarity almost the same as setting your computer audio to 24bit 192000 it's just a driver. I don't know why Google doesn't make this code part of Android it really makes a difference!
It should look like this:
<?xml version="1.0" encoding="UTF-8"?>
<!-- A2dp Audio HAL Audio Policy Configuration file -->
<module name="a2dp" halVersion="2.0">
<mixPorts>
<mixPort name="a2dp output" role="source">
<profile name="" format="AUDIO_FORMAT_PCM_16_BIT"
samplingRates="96000,192000"
channelMasks="AUDIO_CHANNEL_OUT_STEREO"/>
</mixPort>
<mixPort name="a2dp input" role="sink">
<profile name="" format="AUDIO_FORMAT_PCM_16_BIT"
samplingRates="96000,192000"
channelMasks="AUDIO_CHANNEL_IN_MONO,AUDIO_CHANNEL_IN_STEREO"/>
</mixPort>
</mixPorts>
<devicePorts>
<devicePort tagName="BT A2DP Out" type="AUDIO_DEVICE_OUT_BLUETOOTH_A2DP" role="sink">
<profile name="" format="AUDIO_FORMAT_PCM_16_BIT"
samplingRates="96000,192000"
channelMasks="AUDIO_CHANNEL_OUT_STEREO"/>
</devicePort>
<devicePort tagName="BT A2DP Headphones" type="AUDIO_DEVICE_OUT_BLUETOOTH_A2DP_HEADPHONES" role="sink">
<profile name="" format="AUDIO_FORMAT_PCM_16_BIT"
samplingRates="96000,192000"
channelMasks="AUDIO_CHANNEL_OUT_STEREO"/>
</devicePort>
<devicePort tagName="BT A2DP Speaker" type="AUDIO_DEVICE_OUT_BLUETOOTH_A2DP_SPEAKER" role="sink">
<profile name="" format="AUDIO_FORMAT_PCM_16_BIT"
samplingRates="96000,192000"
channelMasks="AUDIO_CHANNEL_OUT_STEREO"/>
</devicePort>
<devicePort tagName="BT A2DP In" type="AUDIO_DEVICE_IN_BLUETOOTH_A2DP" role="source">
<profile name="" format="AUDIO_FORMAT_PCM_16_BIT"
samplingRates="96000,192000"
channelMasks="AUDIO_CHANNEL_IN_MONO,AUDIO_CHANNEL_IN_STEREO"/>
</devicePort>
</devicePorts>
<routes>
<route type="mix" sink="BT A2DP Out"
sources="a2dp output"/>
<route type="mix" sink="BT A2DP Headphones"
sources="a2dp output"/>
<route type="mix" sink="BT A2DP Speaker"
sources="a2dp output"/>
<route type="mix" sink="a2dp input"
sources="BT A2DP In"/>
</routes>
</module>
Will this work on stock n rooted?
moosc said:
Will this work on stock n rooted?
Click to expand...
Click to collapse
My mod or the mod above?
My mod will work with stock rooted, and a custom kernel. Use ES file explorer and a text editor to modify th .XML file and restart. You will notice the difference with good audio. Also WETA audio adds a significant audio gain with the addition of Sony and HTC audio libraries. You don't have to use Dolby Atmos or viper4android that ar included to get these gains. I'm one for not to processed audio viper tends to make the sound signature sound to digital but some of its settings are good for certain situations. That's the link for the WETA mod.
https://www.androidfilehost.com/?fid=745425885120694195
I'm pretty sure I tried aptX mod on stock and it didn't work. You're welcome to try though, it won't break anything.
Sachi, you might want to make a separate thread for your mod and leave it out of this thread.
aptX will increase bandwidth but I'm sure your mod has its merits too.
I did this mod on my Pixel xl rooted with elementalx kernel 1.03 and stock ROM. Worked fine but for some reason when ever the phone went to sleep it would not wake back up.
drzprettyboy30 said:
I did this mod on my Pixel xl rooted with elementalx kernel 1.03 and stock ROM. Worked fine but for some reason when ever the phone went to sleep it would not wake back up.
Click to expand...
Click to collapse
I cannot think of a single reason why that would happen.
I'll try to duplicate this afternoon.
Thanks bro I really loved this mod! Makes my BT headphones Sound so crispy. I know it's the mod causing it because after reverting back it stopped dong it, but will keep testing. Oh I forgot to mention I do have viper audio mod and the dolby Atmos on my Pixel XL. Could that be that issue?
drzprettyboy30 said:
Thanks bro I really loved this mod! Makes my BT headphones Sound so crispy. I know it's the mod causing it because after reverting back it stopped dong it, but will keep testing. Oh I forgot to mention I do have viper audio mod and the dolby Atmos on my Pixel XL. Could that be that issue?
Click to expand...
Click to collapse
I flashed back to stock "V" 7.1.1 image which is the latest.
Then rooted with SuperSU 2.79 SR2.
Then installed ElementalX 1.03.
Then installed the .so aptX files and connected to my aptX headphones.
I am only connecting via A2DP, as expected. aptX does not engage/work at all.
I did verify this via my headphones blue LED which flashes a certain times to indicate A2DP vs. aptX as well as reviewed my catlog which did not indicate aptX was in use.
I also verified no issues with phone going into or waking up from deep sleep.
CZ Eddie said:
I flashed back to stock "V" 7.1.1 image which is the latest.
Then rooted with SuperSU 2.79 SR2.
Then installed ElementalX 1.03.
Then installed the .so aptX files and connected to my aptX headphones.
I am only connecting via A2DP, as expected. aptX does not engage/work at all.
I did verify this via my headphones blue LED which flashes a certain times to indicate A2DP vs. aptX as well as reviewed my catlog which did not indicate aptX was in use.
I also verified no issues with phone going into or waking up from deep sleep.
Click to expand...
Click to collapse
So.. You're saying this mod doesn't work? I'm starting to get impatient with ARISE and this seemed like a great, easy alternative to tide me over.
Alcolawl said:
So.. You're saying this mod doesn't work? I'm starting to get impatient with ARISE and this seemed like a great, easy alternative to tide me over.
Click to expand...
Click to collapse
This mod is for Roms that use the Qualcomm BT stack which stock uses AOSP stack. So no this will not work on stock ROM
Sent from my Pixel XL using Tapatalk
Alcolawl said:
So.. You're saying this mod doesn't work? I'm starting to get impatient with ARISE and this seemed like a great, easy alternative to tide me over.
Click to expand...
Click to collapse
It doesn't work on stock or other ROM's with AOSP bluetooth stack.
It DOES work on ROM's with Qualcomm Bluetooth stack, though so far there is only one to test & verify this with.
Here is Lineage OS ROM and it works on this ROM:
https://forum.xda-developers.com/pixel-xl/help/try-lineage-xl-t3537898
Wouldn't it be possible to simply "copy"/port the Qualcomm BT Stack onto regular AOSP roms? I'm talking replace the libs and confs type of deal...
bmg1001 said:
Wouldn't it be possible to simply "copy"/port the Qualcomm BT Stack onto regular AOSP roms? I'm talking replace the libs and confs type of deal...
Click to expand...
Click to collapse
That would be nice.
Click the link in my signature to monitor the [mostly non-existent] development towards this goal.
Btw, there is a new LineageOS based ROM in the dev forum.
This aptX mod should work on it too.
The ROM is still in Alpha testing though.
https://forum.xda-developers.com/pixel-xl/development/rom-hexa-project-t3544204
CZ Eddie said:
That would be nice.
Click the link in my signature to monitor the [mostly non-existent] development towards this goal.
Btw, there is a new LineageOS based ROM in the dev forum.
This aptX mod should work on it too.
The ROM is still in Alpha testing though.
https://forum.xda-developers.com/pixel-xl/development/rom-hexa-project-t3544204
Click to expand...
Click to collapse
Running it right now and it's pretty nice. Few little nitpicks here and there but amazing for an Alpha.
Sent from my Pixel XL using XDA Labs
Is this apt-x or the new apt-x HD?
scoobydu said:
Is this apt-x or the new apt-x HD?
Click to expand...
Click to collapse
aptX.
I think one of the LG devices has the new HD but it doesn't work on our device.
Does Qualcomm's BT seem more stable or better than stock Android?
Sent from my Pixel XL using Tapatalk
I enable the BT HCI snoop Log option in Dev options...but the Pixel XL does not produce a log file. (My Moto X Pure did fine)
I am trying to get the log file or some app that can read BT info to see what codec it is using to stream media.....
I have read that Pixel doe snot support AptX yet....but I want to see for myself how and what it is using to connect to my devices.
Is there an app that can give that info? with out root...
Anyone?
speedingcheetah said:
I enable the BT HCI snoop Log option in Dev options...but the Pixel XL does not produce a log file. (My Moto X Pure did fine)
I am trying to get the log file or some app that can read BT info to see what codec it is using to stream media.....
I have read that Pixel doe snot support AptX yet....but I want to see for myself how and what it is using to connect to my devices.
Is there an app that can give that info? with out root...
Click to expand...
Click to collapse
Get an iPhone.
speedingcheetah said:
Anyone?
Click to expand...
Click to collapse
I have no idea about Android N, but O does.
Pixel only uses the SBC codec until android O. O supports aptX and a few other high definition Bluetooth codecs.
This I know. But doesn't help the issue of no log. My v10 also will not make a log with option checked and I k ow it supports those codecs.
On Android O....is there an Auto detecting codec setting? or if u manually select codec to use, say LDAC...and if the device does not support it, while it fall back to AptX or SBC?
I ask for anyone on the dev preview to try this and report on it.
I have Sony headphones that support LDAC...but my car headunit only supports AptX.
So would be good to know if i need to switch the setting based on device.
speedingcheetah said:
On Android O....is there an Auto detecting codec setting? or if u manually select codec to use, say LDAC...and if the device does not support it, while it fall back to AptX or SBC?
I ask for anyone on the dev preview to try this and report on it.
I have Sony headphones that support LDAC...but my car headunit only supports AptX.
So would be good to know if i need to switch the setting based on device.
Click to expand...
Click to collapse
It's an auto detect, as my car uses a low level codec, whist my headphones use AptX and it switches itself mate
DaveHTC200 said:
It's an auto detect, as my car uses a low level codec, whist my headphones use AptX and it switches itself mate
Click to expand...
Click to collapse
Still would be great to have a way to detect and see what codec is in use.
No idea why the V10 or Pixel won't produce the log file.
speedingcheetah said:
Still would be great to have a way to detect and see what codec is in use.
No idea why the V10 or Pixel won't produce the log file.
Click to expand...
Click to collapse
I agree.
Take a look here as they did log which codec was used I believe https://forum.xda-developers.com/showthread.php?t=2531440
DaveHTC200 said:
I agree.
Take a look here as they did log which codec was used I believe https://forum.xda-developers.com/showthread.php?t=2531440
Click to expand...
Click to collapse
My Moto X Pure has the files for aptx and aptX hd....but not LDAC. I can confirm via the log and wireshark method that both Aptx/HD work.
I don't think the Moto rom and the Pixel is ASOP based...thats a separate form of android like CM and MIUI....i think. could be wrong...been too long...lol.
speedingcheetah said:
My Moto X Pure has the files for aptx and aptX hd....but not LDAC. I can confirm via the log and wireshark method that both Aptx/HD work.
I don't think the Moto rom and the Pixel is ASOP based...thats a separate form of android like CM and MIUI....i think. could be wrong...been too long...lol.
Click to expand...
Click to collapse
Lol, I can't help much more than that I'm afraid lol
I know O switches but I couldn't tell you about logs etc I'm sorry
Recently learnt that every snapdragon chip has an audio dac in it which is by default disabled in many devices by the oem. How do i know if it is enabled in my device (z2 plus) or not ?
Naveenjain said:
Recently learnt that every snapdragon chip has an audio dac in it which is by default disabled in many devices by the oem. How do i know if it is enabled in my device (z2 plus) or not ?
Click to expand...
Click to collapse
+1
it would be amazing if any dev could enable the inbuilt DAC for audio processing by default...
Use openSL es audio output in vlc, you will instantly feel the difference, it works on stock zui but many custom ROM do not support it.
Thanks for such a good advice. Before i can't even use equalizer but now it works like charm??
Any other method?
if you have rooted your device, you should be able to find a file in the "/" directory named "high_perf_mode" (it will usually be inside a snd_soc_wcd9xx0 folder). If you see the value 0 in it, means it is not enabled. Just change that to "1", save it and reboot your device. You will notice the difference immediately (preferably, test with headphones).
Hope that helps!
DAC means Digital-Analog-Converter. Any device that outputs audio from digital formats have once. What you are referring to is SD has made it's own DAC on SOC which is average not worth anything writing about. There is another thread related to same: https://forum.xda-developers.com/lenovo-zuk-z2/how-to/z2-hifi-sound-quality-t3587221
anmolkakkar said:
if you have rooted your device, you should be able to find a file in the "/" directory named "high_perf_mode" (it will usually be inside a snd_soc_wcd9xx0 folder). If you see the value 0 in it, means it is not enabled. Just change that to "1", save it and reboot your device. You will notice the difference immediately (preferably, test with headphones).
Hope that helps!
Click to expand...
Click to collapse
Verified! Enabled
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.
Hi, I am running ressurection remix 8.1 on my whyred ai, cant seem to work out how to get any bass on my video recordings, on my mido I had to flash some changes to audio mixer files etc. Not sure if anyone else is having this problem but the audio reoding sounds really tinny.
anyone else notice this?
just realised the inbuilt audio recorder is ok, only video apps like google camera and opencamera seem to have the issue?
junglist said:
just realised the inbuilt audio recorder is ok, only video apps like google camera and opencamera seem to have the issue?
Click to expand...
Click to collapse
Same here I also noticed it. Seems they have a high pass filter at around 150Hz or something.
lukesan said:
Same here I also noticed it. Seems they have a high pass filter at around 150Hz or something.
Click to expand...
Click to collapse
yes, thats what I thought too, how the hell do we disable it? anyone?
junglist said:
yes, thats what I thought too, how the hell do we disable it? anyone?
Click to expand...
Click to collapse
Ok found a way to get really good audio quality. I've searched across boards and tried a lot of stuff. The volume level might be low(er) but I need to alter another XML file. Good enough for concerts and out in the open I would say.
First you need to change the max bitrate since they set that to 96KHz which is way to low. The file to edit is /vendor/etc/media_profiles_vendor.xml
Almost all the way down that file you see the AAC settings.
You will see
<AudioEncoderCap name="aac" enabled="true"
minBitRate="8000" maxBitRate="288000"
minSampleRate="8000" maxSampleRate="48000"
minChannels="1" maxChannels="6" />
As you see I set it to 288000.
Next is the biggest issue. Seems the MIUI camera standard uses AGC and that high pass filter that up to date I haven't found. Open camera works but the other microphone you can select they go via the noise cancelling stuff which kills the audio and you get an underwater sound.
I have a official licensed cinema FV-5 from the playstore. Now there is an issue for the moment. I cannot record in 1080P (the image zooms in like crazy it seems, I contacted the developer for that). On 4K recording it works perfectly. Also remember in the menu to tab the little shaky hand to switch on the stabilizer as that works miracles.
Now go to the settings - audio - audio source is set to 'built-in mic(video camera)' ------ audio channels - stereo (2) ----- bitrate - 256000 ----- sampling rate - 48000 and very important 'disable audio automatic gain control - is switched on' meaning disabled.
Give it a go.
@junglist @lukesan Hi,
I downloaded Mi Max 3 ROM which is the same SOC and I found some interesting stuff about that!
mediaprofiles.xml in vendor is the same on both devices (at least on 9.5.19.0 which am using right now) but the one in system is different, on Mi Max 3 they changed the aac bitRate in so many lines from 156000 to 192000 which is looks interesting!
Also there’s a trick here, mediaprofiles.xml which is in system is the same media_profiles_vendor.xml which is vendor, same on our device, that means both files must be overriding not only mediaprofiles.xml in system!
here’s a flashable zip from Mi Max 3 ROM for any one wants to give a try, also check out this video which compares between our device and Mi Max 3 regarding this part:
https://www.youtube.com/watch?v=5LKThf9KWjs (09:42)
I still need to perform more testing before I can confirm if this really works or not!
rocker00 said:
@junglist @lukesan Hi,
I downloaded Mi Max 3 ROM which is the same SOC and I found some interesting stuff about that!
mediaprofiles.xml in vendor is the same on both devices (at least on 9.5.19.0 which am using right now) but the one in system is different, on Mi Max 3 they changed the aac bitRate in so many lines from 156000 to 192000 which is looks interesting!
Also there’s a trick here, mediaprofiles.xml which is in system is the same media_profiles_vendor.xml which is vendor, same on our device, that means both files must be overriding not only mediaprofiles.xml in system!
here’s a flashable zip from Mi Max 3 ROM for any one wants to give a try, also check out this video which compares between our device and Mi Max 3 regarding this part:
https://www.youtube.com/watch?v=5LKThf9KWjs (09:42)
I still need to perform more testing before I can confirm if this really works or not!
Click to expand...
Click to collapse
Ok, very cool find! Observations which I made over the last couple of days
We have 2 'issues' on the redmi note 5 (Whyred) so 1) the bitrate and 2) the highpass
1) is as you say media_profiles_vendor.xml we can easily alter that one. Check out the downloadable MI MIX 2 audio quality ... module for Magisk. Download extract and copy that xml file and set the same permissions 644 I believe. Make a backup of the original first. They set the bitrate really high on that one 256kbit/s I believe which is a bit overkill, but compared to 20mbit/s for the video it is nothing and I rather have overkill than 96kbit/s underwater sound.
So that one is easily fixable.
2) The high pass filter seems to be linked to the AGC. I really like the AGC since it keeps the volume constant and should be the standard for the 'normal' people who do not care about extreme hifi things. I would leave it on if I could only switch off the high pass filter. Shoot a video and it will be perfect for 99.999% of the people. Levels will almost be perfect. People easily understandable etc etc etc.
I would like to switch off the AGC (and the filter) for real audio recordings, meaning classical music etc etc .. this involves always having to check if your level is not to low or if the peaks are not to high causing clipping which means distortion.
For issue 2 the only app that I found that can do this is cinema-fv5. I made an error in my previous text to set it to 8MP since then the stabilization doesn't seem to work properly so I now set that to 2592x1296 which seems pretty 16/9 like to me. If you switch off the AGC in this app then you get AGC off and high pass off. Very low level audio but perfect quality. I guess perfect for a concert. (this weekend there is a local festival here so I can really test (and enjoy))
If you want good audio but mono then you need open camera for now. If you set the microphone to 'mono' you will also hear that the sound is good, setting it to stereo gets the noise cancellation working and it sounds like crap.
I'll try those Mi Max 3 things if I find a bit of time. Lets share knowledge and experience and we'll get it working like it should. This is the only small downside of the redmi note 5 that I have found so far. (and that is coming from an S7)
---------- Post added at 10:54 AM ---------- Previous post was at 10:00 AM ----------
@rocker00 Just flashed it. Does set the bitrate to 288kbit/s which is really high but, like said above compared to video that is peanuts. Better a lot more than what it was. But it does not switch off the AGC or high pass. Since you have the rom can you check and attach another file? The file is in the same path (vendor/ etc) our file on the redmi note 5 is called mixer_paths_skus.xml . I guess it might be a bit different on MI MAX but I guess some more audio is being controlled there.
@lukesan First please override media_profiles_vendor.xml manually because it looks like the script is not mounting vendor!
Regarding the file, media_profiles_V1_0.xml, mixer_paths_i2s.xml, mixer_paths_mtp.xml, mixer_paths_skus.xml, mixer_paths_skush.xml, mixer_paths_wcd9326.xml, mixer_paths_wcd9335.xml and mixer_paths_wcd9340.xml
are the same md5! but mixer_paths.xml (which i downloaded the whole rom just to get it in order to try to enable dual speaker) is completely different!
Also i have 2 doubts:
1- in build.prop which is in vendor they changed ro.vendor.audio.sdk.fluencetype to fluence which is none in our device(related to noise cancelling)
2-ACDB (Audio Calibration Database) which is completely different in Mi Max 3 cuz it has dual speaker and two speakers at the bottom, and ACDB is controlled by audio.primary.sdm660.so which is different for sure in both, i hope it's not related to that because it will be really a hard job!
here's the mixer_paths.xml am still looking into it maybe i can find something!
rocker00 said:
@lukesan First please override media_profiles_vendor.xml manually because it looks like the script is not mounting vendor!
Regarding the file, media_profiles_V1_0.xml, mixer_paths_i2s.xml, mixer_paths_mtp.xml, mixer_paths_skus.xml, mixer_paths_skush.xml, mixer_paths_wcd9326.xml, mixer_paths_wcd9335.xml and mixer_paths_wcd9340.xml
are the same md5! but mixer_paths.xml (which i downloaded the whole rom just to get it in order to try to enable dual speaker) is completely different!
Also i have 2 doubts:
1- in build.prop which is in vendor they changed ro.vendor.audio.sdk.fluencetype to fluence which is none in our device(related to noise cancelling)
2-ACDB (Audio Calibration Database) which is completely different in Mi Max 3 cuz it has dual speaker and two speakers at the bottom, and ACDB is controlled by audio.primary.sdm660.so which is different for sure in both, i hope it's not related to that because it will be really a hard job!
here's the mixer_paths.xml am still looking into it maybe i can find something!
Click to expand...
Click to collapse
Probably it is taking the media_profiles_vendor.xml which I already edited manually. Well to check that our device is capable you could check with Cinema-FV5 lite which is free up to 1280x720 resolution. Disable the AGC and you get a nice clear sound full audio spectrum. I'm on a 8.7.5 rom and when I start to record my image is taken from the upper left corner all zoomed in. Not sure which rom you are on, but could you give that a try?
If it's that *.so file we need to address someone with the right knowledge. I've never decompiled stuff like that.
lukesan said:
Probably it is taking the media_profiles_vendor.xml which I already edited manually. Well to check that our device is capable you could check with Cinema-FV5 lite which is free up to 1280x720 resolution. Disable the AGC and you get a nice clear sound full audio spectrum. I'm on a 8.7.5 rom and when I start to record my image is taken from the upper left corner all zoomed in. Not sure which rom you are on, but could you give that a try?
If it's that *.so file we need to address someone with the right knowledge. I've never decompiled stuff like that.
Click to expand...
Click to collapse
I'll try the app ASAP and i'll keep trying...never give up
BTW, that lib is most likely C++ signed binary so you can't do anything about it!
rocker00 said:
I'll try the app ASAP and i'll keep trying...never give up
BTW, that lib is most likely C++ signed binary so you can't do anything about it!
Click to expand...
Click to collapse
Just came back from the festival that I told about. The default MIUI video cam.. wow made a complete mess. The AGC went completely crazy and no bass. Using cinema-FV5 ... wow listening to it right now with my earplugs..... it's like I'm still there. Ok the bass sounds (only) a bit distorted, but I was standing at the front and the smart people there handed out headphones that dampened sound to the kids. I myself suffer from tinnitus so I have -20dB earplugs ... even then it was crazy loud.
So cinema-FV5 is definitely a must with music. Not sure if I can upload something on Youtube without violating copyrights. But surely this phone is capable of recording high quality audio for sure.
Same happened to me. After recording the stage with artists and loud music. It looked OK, stabilised video at 1080p, but sound lacks bass with stock camera app.
I would like to try better camera apps like gcam, just there are ~50 hours for me to wait till I can unlock my bootloader and flash a decent ROM.
Then we could record at 60fps 1080p and [email protected] with normal audio.
kellerman40 said:
Same happened to me. After recording the stage with artists and loud music. It looked OK, stabilised video at 1080p, but sound lacks bass with stock camera app.
I would like to try better camera apps like gcam, just there are ~50 hours for me to wait till I can unlock my bootloader and flash a decent ROM.
Then we could record at 60fps 1080p and [email protected] with normal audio.
Click to expand...
Click to collapse
Forget gcam or other roms for now since they use the same audio path. There is another trick I read about but it involves a lot of work and I would hardly call it a working thing unless you spend a lot of time. Check this thread. I know for the MI MIX but same procedure applies for now. https://forum.xda-developers.com/mi-mix-2/how-to/mi-mix-2-video-sound-recording-quality-t3776450
Leave the 60fps and 4K behind if it is in a dark environment. You might end up with dropped frames etc which is really annoying.
lukesan said:
Forget gcam or other roms for now since they use the same audio path. There is another trick I read about but it involves a lot of work and I would hardly call it a working thing unless you spend a lot of time. Check this thread. I know for the MI MIX but same procedure applies for now. https://forum.xda-developers.com/mi-mix-2/how-to/mi-mix-2-video-sound-recording-quality-t3776450
Leave the 60fps and 4K behind if it is in a dark environment. You might end up with dropped frames etc which is really annoying.
Click to expand...
Click to collapse
Have you tried it? I've tried your trick with the bitrate increase in media_profiles.xml, though I've set it to 192000 and used the FV-5 disable the AGC and it's much better quality! Although the bass is a bit too much pronounced and the meds and highs are a bit sacrificed, it's still much better than stock. But with the custom settings for audio in FV-5 it makes that "underwater" sound, no matter which combination I used, but I did everything according to your post, only if I leave the default values it works. (I now suspect it was maybe because of the stereo recording option)
I am interested to make some changes using the thread you linked, I'm just afraid not to make a mess of volumes in earpiece or introduce echo during a call or something like that, that's why I'm hesitating.
The AGC makes a total mess of recording, it lowers the quality and introduces background noise.
For the 60fps I'm not sure that works as none of the camera app that I've tried are able to record it (I'm on AOSP based rom) because it depends on the camera blobs, and I'm not sure Xiaomi updated the sources, but they did introduce it in MIUI 10 builds.
Cirra92 said:
Have you tried it? I've tried your trick with the bitrate increase in media_profiles.xml, though I've set it to 192000 and used the FV-5 disable the AGC and it's much better quality! Although the bass is a bit too much pronounced and the meds and highs are a bit sacrificed, it's still much better than stock. But with the custom settings for audio in FV-5 it makes that "underwater" sound, no matter which combination I used, but I did everything according to your post, only if I leave the default values it works. (I now suspect it was maybe because of the stereo recording option)
I am interested to make some changes using the thread you linked, I'm just afraid not to make a mess of volumes in earpiece or introduce echo during a call or something like that, that's why I'm hesitating.
The AGC makes a total mess of recording, it lowers the quality and introduces background noise.
For the 60fps I'm not sure that works as none of the camera app that I've tried are able to record it (I'm on AOSP based rom) because it depends on the camera blobs, and I'm not sure Xiaomi updated the sources, but they did introduce it in MIUI 10 builds.
Click to expand...
Click to collapse
Strange that you got the underwater sound. Can you check with this one? https://mediaarea.net/en/MediaInfo Just drag and drop the file on it. It will show the audio properties.
Just to confirm again my settings in FV-5 I changed the resolution to 2592x1296 (turn on handshake thing on where you can actually see where you are recording, weird setting I know). In the 'Audio' settings check the attached screenshot.
lukesan said:
Strange that you got the underwater sound. Can you check with this one? https://mediaarea.net/en/MediaInfo Just drag and drop the file on it. It will show the audio properties.
Just to confirm again my settings in FV-5 I changed the resolution to 2592x1296 (turn on handshake thing on where you can actually see where you are recording, weird setting I know). In the 'Audio' settings check the attached screenshot.
Click to expand...
Click to collapse
Oh yes I did that, but you didn't check the "Custom audio settings" box so the app uses default system settings rather than the ones you selected. Try it out if you didn't already.
And I've checked with MediaInfo, the video was recorded in 96K (because the app didn't use custom settings), but anyway it should be using maximum possible values the device has set in media_profiles_vendor.xml, which is in my case 192K. I've seen now that media_profiles_V1_0.xml is basically the same file and there is 96K set as maximum, maybe both files need to be changed?
Cirra92 said:
Oh yes I did that, but you didn't check the "Custom audio settings" box so the app uses default system settings rather than the ones you selected. Try it out if you didn't already.
And I've checked with MediaInfo, the video was recorded in 96K (because the app didn't use custom settings), but anyway it should be using maximum possible values the device has set in media_profiles_vendor.xml, which is in my case 192K. I've seen now that media_profiles_V1_0.xml is basically the same file and there is 96K set as maximum, maybe both files need to be changed?
Click to expand...
Click to collapse
That's normal since it seems you can't overwrite those settings in our current roms it seems. I bought that FV5 but I emailed support and never gotten answer back, to bad. It always takes the settings from that file on the phone it seems. And yes if you see 96Kb/s than it is normal that you hear these metallic sounds. Can you maybe attach the media_profiles_vendor.xml you have in the /system/vendor/etc dir?
lukesan said:
That's normal since it seems you can't overwrite those settings in our current roms it seems. I bought that FV5 but I emailed support and never gotten answer back, to bad. It always takes the settings from that file on the phone it seems. And yes if you see 96Kb/s than it is normal that you hear these metallic sounds. Can you maybe attach the media_profiles_vendor.xml you have in the /system/vendor/etc dir?
Click to expand...
Click to collapse
Well recording in 96K instead of 48K which was the case with MIUI 9.5 in GSMArena test is already an improvement, however I'm sure this device is capable of even more. So for now, seems that just disabling AGC made a very good difference, it might just get better if we raise the bitrate even more. I've seen in the thread you linked that they actually modified media_profiles_V1_0.xml in case of LineageOS to raise the bitrate, I will now try that one as well.
Here is my file you requested.
lukesan said:
That's normal since it seems you can't overwrite those settings in our current roms it seems. I bought that FV5 but I emailed support and never gotten answer back, to bad. It always takes the settings from that file on the phone it seems. And yes if you see 96Kb/s than it is normal that you hear these metallic sounds. Can you maybe attach the media_profiles_vendor.xml you have in the /system/vendor/etc dir?
Click to expand...
Click to collapse
I confirm that changing the media_profiles_v1_0.xml does increase the bitrate! I have set it to 192K, however since the maximum value that was set for each resolution (I've tested 1080p) is 156K the app used that one based on previous setting. Now every app should use the 156K if we don't alter the bitrate for each resolution separately (that's my guess at least).
lukesan said:
Just came back from the festival that I told about. The default MIUI video cam.. wow made a complete mess. The AGC went completely crazy and no bass. Using cinema-FV5 ... wow listening to it right now with my earplugs..... it's like I'm still there. Ok the bass sounds (only) a bit distorted, but I was standing at the front and the smart people there handed out headphones that dampened sound to the kids. I myself suffer from tinnitus so I have -20dB earplugs ... even then it was crazy loud.
So cinema-FV5 is definitely a must with music. Not sure if I can upload something on Youtube without violating copyrights. But surely this phone is capable of recording high quality audio for sure.
Click to expand...
Click to collapse
I tried this app with the steps you mentioned and yeah, sound is better for sure but it's much better if we can get the same result on stock cam.
let's take it step by step, first is the bit rate, even after using Mi Max 3 files the bit rate remains the same! i checked my old Sony Xperia z2 mediaprofiles.xml and i found the aac bitRate is also 192000, see the video sample result in the 1st pic from sony and second one from note 5 pro!
Now clearly there's something controlling the cam audio beside mediaprofiles.xml since the modifications wasn't enough!
I'll record a log while recording and let's see if i can find any info about that!
@Cirra92 60 FPS is working on 9.5, i thought like you about blobs but surprisingly no! now i'm on 9.5.19.0 and i just got the camera apk from MIUI 10 and i have 60 FPS!
Also i found another thing which is interesting but it's still not working even on Mi Max 3.....looks like 120 FPS HFR is on the way!
Check this video out: https://www.youtube.com/watch?v=0rjZx_5JD1s (13.06)
I managed to get this setting even if it's still grey!
etc\device_features/whyred.xml just added those lines:
<!--whether support camera video high frame-->
<bool name="support_camera_video_high_frame">true</bool>
let's try to make the cam perfect as much as possible!