Audio broken after audio policy conf edit - Android Q&A, Help & Troubleshooting

As the title says i have edited the audiopolicy.conf file of my android 5.1 bluboo xtouch(a cheap chinese phone) i just used xplore with root, now i increased the step from 100 to 110 and from that on my audio is crazy soft and makes the familiar crack sound when you plug in a speaker or headphones for the first time(but 10x louder), but now it does it every time i play a sound and wait a moment then the first sound after this halt will have the crack too; so i was huh, maybe the scale of volume works from 0 to 1 so step time the scale so 0.5(50% volume) would be (110 scale) 55, and i changed it accordingly to 80 step size this didn't change the problem with the crack and still my sound is really really quiet i modified most thing i changed: max volume,min volume and step size to no use.
I realised this was not going to be fixed through a text editor and reinstalled my scatter file note: ( I did not install these parts: Userdata, Cache, Recovery, Boot) chache i wiped before boot again so would matter anyway. but then the same issues pesisted only now i nolonger have root 1 supersu zip later and it seems my audio policy has been restored to the januari 2016 variant but still the problem pesists.
headphone plug has same issue*
Now i turn to xda, any clues? i have googled but could not find a similair problem is my dac broke?

Related

INFO: TPA2051 Audio Amplifier and TPA2051_CFG.csv

On our phones, and several others, the audio subsystem is made up of several different chips.
The one we (in CM10-land) are most interested in, is the TPA2051, as this is the AMP circuit, that controls volume.
It's run over I2C and configured by a file known as TPA2051_CFG.csv
Other versions of the file are present on the phone, but according to logcat, the CFG.csv version is the one actually 'fed' to the DSP.
The thing is, the format of this file is NOT documented... There is some info out there on the net, but it was written by a non-english-speaker who prefers to tell you to 'google' relevent references on HOW he did what he did.
SO, here we go, on what this file does:
1) Format:
It's a comma-separated-value file (CSV), which will open in Excel if you try to read it on your PC. This makes it into a nice, pretty table-format.
It is formatted by column, as follows:
# Device, Type, Fault Register, Amplifier Control, Auto-Gain Attack, Auto-Gain Release, Mic Gain, Stereo-Out Gain, Headphone Out Gain
HTC Documents the 'Types' and the Device #s in the file.
However they do not document the register-values themselves - perhaps because you can DESTROY your phone's speakers, your headphones, or your ears if you mess them up.
Fortunately, there is a data-sheet, which I have ATTACHED to this post rather than telling you to google it.
In that data sheet, starting on PAGE 16, there are detailed descriptions of the register values.
Register 0 is read-only (it's the way the chip tells you something's broke), 1-6 are writable.
To write a value to the register, you use the tables from the datasheet, and a base-converting calculator (Such as the Windows Calc in 'Programmer mode'.
For each value you want to change, start with the calc in binary, and 'set' the settings you want in that register by using '1' for 'off' and '0' for 'on'.
Then click the 'hex' button to convert to Hex, for placement in the TPA2051_CFG.csv file.
You are going to want to edit the file in Linux, Cygwin, or on the phone over ssh (vi and other editors do not work in adb), because Windows still sticks that stupid ^M on the end of every line...
For example, to set Register 1 to:
'Speaker-Mode Volume Limiter, Volume Limiter Disabled, <Reserved>, Not Shutdown, Headphone Left Off, Headphone Right OFF, Speaker On, No Bypass'
You would enter
10000010
into the calculator
You would then convert it to HEX, which would give you
82
Which is written into the .csv file as 0x82
With that primer, the Page 16 info should be easy to understand.
Note, according to the near-uninteligable original author that cued me in on this, one should not set Stereo Out gain higher than 0x59 and should not set Headphone Out higher than 0x50 or at the extreme 0x55!
0x59 stereo gain formats to:
SPK_Gain: Low (6db)
HDPHN Gain: 0db
<reserved> (Error, should not be set at 0x59 but is in his example)
Stereo Volume (Binary): 11011 (+14dB)
Now, this means that 'Mr Non-English's' recommendation does not quite match up to the docs, as these 0x numbers are HEX ENCODED BINARY (so a bigger HEX may not mean a higher volume), and he sets RESERVED bits... But I'm just sayin... Be careful!
Thanx alot for the detailed info. Im not a dev and I understood about half of what was said but it seems you took initiative and time to collect this info. All info is good info especially when it comes to something that can affect speaker performance. I blew the speakers on many a v3 RAZR back in the day from tweaking things a little too much. Again much thanks.
I pulled these from [ROM][JB] Unofficial CyanogenMod 10 [4.1.2]. Copied the files to /system/etc/ set permissions to rw- r-- r-- and rebooted the phone. I notice no difference in call volume, no changes occurred while using the rocker -/+ on the side of the phone. But it could be a placebo effect, the audio sounds better while playing Pandora, less distortion. I no longer have echo during calls.
.rar contains 3 files:
TPA2051_CFG
TPA2051_CFG_XC
TPA2051_CFG_BEATS_HW (This one is not included in our CM10 for the Amaze, which by the title I feel its related to the installation of Beats and not necessary for this test).
I do not have a PC available to compare these to the originals.
Hope this helps the cause.
rfunderburk39 said:
I pulled these from [ROM][JB] Unofficial CyanogenMod 10 [4.1.2]. Copied the files to /system/etc/ set permissions to rw- r-- r-- and rebooted the phone. I notice no difference in call volume, no changes occurred while using the rocker -/+ on the side of the phone. But it could be a placebo effect, the audio sounds better while playing Pandora, less distortion. I no longer have echo during calls.
.rar contains 3 files:
TPA2051_CFG
TPA2051_CFG_XC
TPA2051_CFG_BEATS_HW (This one is not included in our CM10 for the Amaze, which by the title I feel its related to the installation of Beats and not necessary for this test).
I do not have a PC available to compare these to the originals.
Hope this helps the cause.
Click to expand...
Click to collapse
replace your files. zip. and the speaker works in calls, the sound has improved low contrast. very good contribution.
This looks very interesting but I don't fully understand it. Is this just a way to change the volume level values on your phone to make it louder or lower?

KGL unit + FiiO = fail

Hey, all.
I installed Malaysk's latest ROM on my Eonon GA5151F. It's one of the HuiFei units for a Mazda. Instantly I noticed the sound quality is garbage and am determined to turn it around. On second thought, it might a KDL type unit ... it doesn't actually say under hardware info.
I followed aluver's awesome advice on getting USB audio working after finally getting a FiiO E18 in the mail.
I'm stuck: I can only play via UAPP (USB Audio Player Pro) and even when I do play in UAPP, the sound quickly becomes jumbled and distorted. If I set to 25ms for the buffer, I get about 20 seconds of play time before it crashes.
I've tried a regular 1m cable and even a tiny, short .25m cable but no change.
I do see that I have better luck using alluver's provided audio.primary.rk30board.so file but that only gives me the 20 seconds of play time. That file is 133K in size while the one installed on the unit (or maybe it's from the Malaysk ROM) is 213K. I did not see anywhere in my unit's file to edit and hard write the pcmC2D0c.
Any ideas?
Note: I see a similar thread of a similar issue but thought it would be rude to light back.
I tried to open up the unit but the CD drive is preventing me from getting a good look in. The USB cable that runs from inside to outside the unit is quite long. Seems like it might actually be 1.5 meters.
How can I get in there to pull this thing out and try a short cord? Or should I look in to a powered USB hub (such as the one sold by Carnetix)?
How interesting: I purchased a 7-port powered USB hub (these are quite hard to find in stores!) and now it works! I just plugged the thing in and connected a regular 1m cable to the hub and FiiO and UAPP plays without issue. I did have to enable the first two tweaks in the settings but it's a good start.
Issue continues though: only UAPP will play for me. I am guessing this is a driver issue but not sure where to begin on solving this.
Also, if I have the device turned on while the head unit boots, the head unit sits in safe mode.
@supaneko
Congradulations! Now you have enough power to supply your E18.
About how to make it possible all android sounds going to E18 without UAPP.
All ROMs higher than 4.2 android have audio.primary.rk30board.so file without that numbers to change - it's dynamic.
I have found the other way on 4.4 to make sound routing. It's more right way. Through ALSA.
But I'm not sure I can write a guide now, because I can't remember all I did in details.
And, secondly, I hope there is a more simple way, that was founded by kumarai, that I did not tested yet. His solution is to use system.img from KGL_rk3188_h(20151019) in his ROM. He says he just copied my drivers and wrote insmod strings to install-recovery.sh and all works flawlessly, with hot-plug, as I have working too.
Here is his post with that custom ROM on russian KGL HU forum http://4pda.ru/forum/index.php?showtopic=704299&view=findpost&p=45437941
You can try it (at your own risk, of course)
aluver, your kindness is contagious. Thank you for that.
I will try the link you provided and report back. I'm guessing flashing system.img shouldn't kill me because I can always reflash if needed.
At this point, I am still super determined to get this working. You've helped me in the right direction, aluver. Thanks again!
Well .... I thought that would be useful but I am on an RK3188 unit and then, it also dawned on me, I have the latest Malaysk ROM running. I was thinking I could just install this and extract the install-recovery.sh but it's not for the same unit.
I downloaded the update.rar listed and it only had an update.img in it. I tried to extract it using simg2img but it gives me an error.
I've PM'ed kumarai on here in hopes that he can help me out.
I'll give it another go tomorrow.
@supaneko
Oh, sorry, I thought you have RK3066. That image is not for RK3188 HU of course. But I think it makes things simpler. The trick of kumarai was exactly RK3188 system.img. It must work on RK3188 ROM "from the box" with your HU...
You just need to check what system.img version (date) Malaysk has used for the ROM you have. Or just give me a link to your ROM version. I'll check it by myself.
I use RK3xxx Firmware Tools for unpacking Rockchip update.img, system.img, boot.img & recovery.img
aluver said:
@supaneko
Oh, sorry, I thought you have RK3066. That image is not for RK3188 HU of course. But I think it makes things simpler. The trick of kumarai was exactly RK3188 system.img. It must work on RK3188 ROM "from the box" with your HU...
You just need to check what system.img version (date) Malaysk has used for the ROM you have. Or just give me a link to your ROM version. I'll check it by myself.
I use RK3xxx Firmware Tools for unpacking Rockchip update.img, system.img, boot.img & recovery.img
Click to expand...
Click to collapse
I am using the latest (posted here anyway) Malaysk ROM for 800x480 RK3188: https://yadi.sk/d/R0RY7sxbmmuwi
I located the RK3xxx Tools but .... they're for Windows and I'm on Linux. :\
I'd appreciate the help, aluver.
I have compared system folders of ROMs from kumarai and yours from the link you provided.
They are differ by files at /system/lib
but files at /system/lib/hw are the same
I think something in libaudioflinger.so or other library at /system/lib may do the trick with sound routing.
kumarai's system version 20151012.145613
yours - has a later date - 20151130.180905
Don't understand what's wrong with it...
Now I going to find Malaysk's ROM with same version of system.img as kumarai has.
Can't find needed version among Malaysk's ROMs. Looks like he didn't use that.
The previous to yours version has 20150824.182544 system.img only.
But I have another solution for routing for now.
You can replace audio.primary.rk30board.so by my patched version (already tested on RK3188). Do a backup of the original file, check it's permissions before.
Copy attached audio.primary.rk30board.so to /system/lib/hw folder and change permissions to original file had.
Power off HU and wait few minutes it complitely turned off.
After Power on check the sound is going to DAC (you may hear effect even without reboot - just after replacing the file).
If you will have a problem with sound stucks after some time, you'll need to edit /etc/audio_policy.conf (make backup first)
Delete whole this alsa_usb part of it:
Code:
alsa_usb {
outputs {
alsa_usb {
sampling_rates 44100|48000
channel_masks AUDIO_CHANNEL_OUT_STEREO
formats AUDIO_FORMAT_PCM_16_BIT
devices AUDIO_DEVICE_OUT_ANLG_DOCK_HEADSET|AUDIO_DEVICE_OUT_DGTL_DOCK_HEADSET
}
}
inputs {
alsa_usb {
sampling_rates 8000|11025|16000|22050|32000|44100|48000
channel_masks AUDIO_CHANNEL_IN_MONO|AUDIO_CHANNEL_IN_STEREO
formats AUDIO_FORMAT_PCM_16_BIT
devices AUDIO_DEVICE_IN_ANLG_DOCK_HEADSET
}
}
}
Because it can make a conflict. Reboot is needed to take effect.
By the way, did you have checked insmod's result? It must load all 4 modules *.ko without any errors.
Good luck and post any information about your progress.
SUCCESS!!
The insmod commands were already in there thanks to your original post, aluver. I replaced the .so file originally supplied in that post with what you attached here and ... it works! The ALSA lines were already in there so I didn't need to change that.
IT WORKS! I am terribly excited.
One final thing: if I have the FiiO device turned on when the Android boots, the unit boots into Safe Mode. I suspect there might not be much of a solution for this. Any ideas, aluver?
Alright. Made the drive home and ... it kept on working! I am so happy, aluver. Thank you.
I saw in another thread a mention about the volume control not working. This does indeed seem to be the case for me as well. I tried using the alsa_amixer command in Terminal but get a "Command not found" error when I do.
Out of curiosity, what DSP do you use, aluver?
supaneko said:
The ALSA lines were already in there so I didn't need to change that.
Click to expand...
Click to collapse
You didn't understand - You have to DELETE all that strings I wrote from audio_policy.conf and save it. They make a conflict I think.
supaneko said:
One final thing: if I have the FiiO device turned on when the Android boots, the unit boots into Safe Mode. I suspect there might not be much of a solution for this. Any ideas, aluver?
Click to expand...
Click to collapse
I think this problem should gone, if you delete strings from audio_policy.conf as I told you.
supaneko said:
Alright. Made the drive home and ... it kept on working!
Click to expand...
Click to collapse
Sorry, can't understand this... What drive?
supaneko said:
I saw in another thread a mention about the volume control not working. This does indeed seem to be the case for me as well. I tried using the alsa_amixer command in Terminal but get a "Command not found" error when I do.
Click to expand...
Click to collapse
Did you install Alsamixer from google play? It must be installed before use of mtc-service and\or alsa_amixer commands.
I think we need to make sound routing scheme better. As for me, I made it through alsa, not by replacing digits in audio.primary.rk30board.so.
With alsa configuring, we can make lossless 24bit volume control. Now we have a dynamic range losses because of 16bit volume control only.
Each -6dB from max digital volume are equal to 1-bit of bit depth loss.
I.e. if you listening music at volume position 10 of 30, it is about -40dB, you hear about (16bit - 40/6)~=10bit sound only!
But we know that a human's ear is logarithmic, so we can hear this losses.
To prevent that we can do the trick with adding amount of zero LSBs to make 24bit sound from 16bit source.
Then the digital volume will not become by fear for us.
Sorry for my English. I hope you understand.
supaneko said:
Out of curiosity, what DSP do you use, aluver?
Click to expand...
Click to collapse
I have russian amplifier with built-in modified by myself 8-channels DSP, based on 2 chips Analog Devices ADAU1701. But this DSP is not "for all". The sound processing algorithms for it I build in SigmaStudio. This is hard for usual people, but is very interesting for me .
The chain is: HU RK3066 Android 4.4.4 -> HiFiMeDIY Sabre U2 24/96 USB-DAC -> toslink -> Ryazanpribor X1 mkII (w/mod DSP X5 8channels)-> Focal Performance PS165FX, P25F+Pioneer GM-D8601
aluver said:
You didn't understand - You have to DELETE all that strings I wrote from audio_policy.conf and save it. They make a conflict I think.
I think this problem should gone, if you delete strings from audio_policy.conf as I told you.
Sorry, can't understand this... What drive?
Did you install Alsamixer from google play? It must be installed before use of mtc-service and\or alsa_amixer commands.
I think we need to make sound routing scheme better. As for me, I made it through alsa, not by replacing digits in audio.primary.rk30board.so.
With alsa configuring, we can make lossless 24bit volume control. Now we have a dynamic range losses because of 16bit volume control only.
Each -6dB from max digital volume are equal to 1-bit of bit depth loss.
I.e. if you listening music at volume position 10 of 30, it is about -40dB, you hear about (16bit - 40/6)~=10bit sound only!
But we know that a human's ear is logarithmic, so we can hear this losses.
To prevent that we can do the trick with adding amount of zero LSBs to make 24bit sound from 16bit source.
Then the digital volume will not become by fear for us.
Sorry for my English. I hope you understand.
I have russian amplifier with built-in modified by myself 8-channels DSP, based on 2 chips Analog Devices ADAU1701. But this DSP is not "for all". The sound processing algorithms for it I build in SigmaStudio. This is hard for usual people, but is very interesting for me .
The chain is: HU RK3066 Android 4.4.4 -> HiFiMeDIY Sabre U2 24/96 USB-DAC -> toslink -> Ryazanpribor X1 mkII (w/mod DSP X5 8channels)-> Focal Performance PS165FX, P25F+Pioneer GM-D8601
Click to expand...
Click to collapse
You amaze me, aluver. Again, thank you.
I installed Alsamixer AND the modified MCT service app. Volume control is working! There is one bug though: when I hit the volume up or down, a + and - toast pops up. The problem is that if I go from a volume of 30 down to 0, this +/i will pop up 30 times ... that's along with the volume bar at the bottom of the screen. I can turn it off by turning off the Media keys option in MCT but doing that kills, well, the media keys.
Also, I removed the lines specified from audio_policy.conf. If the FiiO is turned on while Android boots, it still goes in to Safe Mode. I did notice that after removing those lines, I started to get crackling, hissing, and just overall poor sound quality so I re-added the lines and the problems went away. It's still TOO QUIET though!
How can I make these changes you mention in ALSA? I have some sharp hearing myself and it's driving me nuts that things just don't sound as good as they should. I am curious to see your own ALSA parameters.
Quite the setup you have, aluver. I find it inspiring. One day, maybe I'll have the patience to program my own slopes and equalizations. We'll see.
supaneko said:
You amaze me, aluver. Again, thank you.
I installed Alsamixer AND the modified MCT service app. Volume control is working! There is one bug though: when I hit the volume up or down, a + and - toast pops up. The problem is that if I go from a volume of 30 down to 0, this +/i will pop up 30 times ... that's along with the volume bar at the bottom of the screen. I can turn it off by turning off the Media keys option in MCT but doing that kills, well, the media keys.
Click to expand...
Click to collapse
I am glad to help somebody, who has a good target About a + and - toast popups - it can be disabled in the code of mtc-service. I do not like that too, but have no time to make this job.
supaneko said:
Also, I removed the lines specified from audio_policy.conf. If the FiiO is turned on while Android boots, it still goes in to Safe Mode. I did notice that after removing those lines, I started to get crackling, hissing, and just overall poor sound quality so I re-added the lines and the problems went away. It's still TOO QUIET though!
Click to expand...
Click to collapse
It is very interesting effect.... I can't explain it yet. Let's try to determine the problem's cause by looking at logs. Just install CatLog from google play and try to show me what happens at start of HU with FiiO turned on.
supaneko said:
How can I make these changes you mention in ALSA? I have some sharp hearing myself and it's driving me nuts that things just don't sound as good as they should. I am curious to see your own ALSA parameters.
Click to expand...
Click to collapse
Sorry, but I cannot write it right now. I need to collect all information and copy changed drivers from my HU. Then I going to do a full guide. I made my installation at summer, and I am affraid to forget some details.
supaneko said:
Quite the setup you have, aluver. I find it inspiring. One day, maybe I'll have the patience to program my own slopes and equalizations. We'll see.
Click to expand...
Click to collapse
Thank you. All is in our hands. Keep moving
I forgot about "too quiet". Didn't you install any android mixers or volume regulators?
aluver, I haven't forgotten. Been a very busy week.
I got a new DSP and put that in (though not as fancy as your's ). Totally resolved my volume/gain issues but I'm wondering: what do you mean about the volume and the bits changing from 24?
I installed CatLog and when I did a reboot with the DAC powered on, the unit got stuck in a bootloop. It's never done that before. I'll have to give it a try again tomorrow or figure out what's changed to cause that. I'll report back again soon.
Thanks again, aluver!
@supaneko
What DSP did you get? Does it have a remote volume control unit? And what's the cause for volume/gain issues?
About bit depth and volume - read this http://www.head-fi.org/t/671220/eff...e-to-keep-software-at-full-volume-is-nonsense
That is why I say we need 24bit for the lossless volume regulating within HU.
If you have DSP with remote control unit now, you better use that, because it has 56 or 64 bit of internal processing deph (Volume at HU must be 100%).
About a bootloop. You can try to comment the 4 usb-audio driver insmod strings in install-recovery.sh (check the permissions after that! do not lose root!), then reboot without them, run catlog, and then type insmod commands at terminal emulator (don't forget "su" at first), and see what happens in catlog.
aluver said:
@supaneko
What DSP did you get? Does it have a remote volume control unit? And what's the cause for volume/gain issues?
About bit depth and volume - read this http://www.head-fi.org/t/671220/eff...e-to-keep-software-at-full-volume-is-nonsense
That is why I say we need 24bit for the lossless volume regulating within HU.
If you have DSP with remote control unit now, you better use that, because it has 56 or 64 bit of internal processing deph (Volume at HU must be 100%).
About a bootloop. You can try to comment the 4 usb-audio driver insmod strings in install-recovery.sh (check the permissions after that! do not lose root!), then reboot without them, run catlog, and then type insmod commands at terminal emulator (don't forget "su" at first), and see what happens in catlog.
Click to expand...
Click to collapse
@aluver, I picked up an AudioControl DQDX. It has a remote control but it only controls the bass or sets the various delays and other settings. I am thinking of swapping out the DAC I picked up with another single DIN head unit that supports DAC. That way, I can control the volume with an analog dial and still have steering wheel controls work. That's down the road though. I need to upgrade my amp and some other items first. Might just use the volume control on the DAC I picked up for now.
I'll post the CatLog logs in a bit. Thanks again, aluver.
Wow, your DSP is very rare in my world AudioControl's conceptuality is a vintage radicalism.
I don't understand why are you going to swap your DAC with a single DIN HU. In most cases analog volume control can't be used when you build a system with DSP. And analog volume control has it's own noise...
I think you better have to think about swapping of DSP. Something like Helix DSP Pro or anything else, more widely using our time.
About using the volume control on the DAC - You better have to connect your DSP and DAC by digital interface if you don't want to kill the sound by needless DA-AD conversions.
You make me laugh, aluver.
Yeah, one day I'll have the cash for a Helix DSP but ... for now ... I have to be budget conscious. Helix DSP is certainly in the plans though. Just gotta get the "eaiser" stuff like this Android head unit working first!
Again, I'll post the logs later!
aluver, I'm looking over the specs of the Helix DSP and ... wow. I'm impressed. I've added it to my bucket list. Will have to pick one up after I swap out my speakers for better ones.
Those Focal's you run, did you find them too bright at all? I've heard the Focals can be a little bright and I am sensitive to the higher freqs.

Touch sounds not working on my Android 6.0.1 speakers.

Hi,
My model is CAT S60 (recently bought) and I am having issues with touch sounds as there are none. I have looked up other threads and i tried Volume control + and Audio manager to increase the system sound but it's already on max and still there is no sound.I had no issues with the sound when I got it, but now there is no sounds. The lock/unlock sound is also somewhat silent now. Although when I use earphones, the touch and lock sounds work properly. I have done factory reset and hard reset 5 times now but in vain.
In addition to this, there is 1 more peculiarity but i am not sure if it is related to my main issue or not, i.e when i connect my phone to my pc (mtp ) i can access my internal storage but it doesnt show the memory available as it did earlier.
Kindly help me with this issue.
Thanks

Audio very soft after audio policy conf change

As the title says i have edited the audiopolicy.conf file of my android 5.1 bluboo xtouch(a cheap chinese phone) i just used xplore with root, now i increased the step from 100 to 110 and from that on my audio is crazy soft and makes the familiar crack sound when you plug in a speaker or headphones for the first time(but 10x louder), but now it does it every time i play a sound and wait a moment then the first sound after this halt will have the crack too; so i was huh, maybe the scale of volume works from 0 to 1 so step time the scale so 0.5(50% volume) would be (110 scale) 55, and i changed it accordingly to 80 step size this didn't change the problem with the crack and still my sound is really really quiet i modified most thing i changed: max volume,min volume and step size to no use.
I realised this was not going to be fixed through a text editor and reinstalled my scatter file note: ( I did not install these parts: Userdata, Cache, Recovery, Boot) chache i wiped before boot again so would matter anyway. but then the same issues pesisted only now i nolonger have root 1 supersu zip later and it seems my audio policy has been restored to the januari 2016 variant but still the problem pesists.
headphone plug has same issue*
Now i turn to xda, any clues? i have googled but could not find a similair problem is my dac broke? did the speaker fry?

Low volume after a while

Hello guys, coming from Zuk Z2 i'm now part of your community. Sorry if my english is not perfect, i'm not a native speaker, feel free to correct me or ask what i mean if you couldn't understand something properly.
So problem is, after a few minutes of listening to music (99% Spotify) my volume suddenly become low. From my experiences with my older phones, it seems to me like dialog pop-up box showed up saying my volume is too high for my ears (you know what i mean, high volume warning). But i disabled it. Weird. Only restart helps but only for a short moment.
Thing is, right from the start of using this phone, i didn't like low volume on headphones specifically in Spotify. So i followed this guide:
https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-headphone-volume-increase-t3711247
I followed only first two steps - for disabling high volume warning limit.
Next files or folders i couldn't find , for example " /product/etc/audio/hi6403 " but that seems to be problem of my current android and emui version.
I'm using Android 8.0, Emui 8.0 , rooted with Magisk and with TWRP.
Next weird thing is, my phone is missing Huawei Histen 3D Audio.
After fresh install and setting up my phone i followed this guide:
https://forum.xda-developers.com/honor-6x/how-to/guide-list-bloat-software-emui-safe-to-t3700814
Tell me please if something from the list could remove, or possibly damage my volume.
Thanks in advance. Have a nice day.

Categories

Resources