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.
Related
I've already looked around at various options for boosting the volume on the phone, and I've run into issues at every point:
I've seen people reply to these threads saying that it's the headphones at fault: My headphones are fine. I'm comparing volume to an HTC Desire, and the SGS2 is distinctly lacking. And yes; I have plugged my headphones in fully
Another common reply seems to be that MIUI volume is higher than Stock so there is no issue. There is an issue: it's quieter than an HTC Desire!
Using *#197328640# to access Service Menu -- I'm running MIUI and therefore do not have the stock dialer, so codes don't seem to work. I could flash the stock ROM, do the code, fix the volume, but apparently the setting is lost after reboot -- so flashing MIUI after that is certainly going ot lose any settings.
I had a go with a couple of apps off the market, with low expectations, and they didn't work either.
I'm rooted (of course) and reasonably tech-savvy so I'm quite comfortable with a Linux system and ADB, quite happy to hack and patch. Is there any (permanent) fix I can apply to increase the volume? I'd prefer something fairly elegant, like applying the Service Menu options manually (somehow) at boot.
Have you tried Voodoo Louder?
Great tip, I wonder how I didn't find a reference to Voodoo before... I just bought the app and it seems to be working as expected!
Thanks a lot I'll test it through the day!
try the fix that in my signature then if u like to use voodoo louder u ear will blown lol
^^
+10000000000000 this ;-) Have been using Yahyoh's fix for a while now, have tried Voodoo Louder but this little app increases volume much more & also gives a "fuller"/less hollow sound.
Thanks for this info yahyoh, it's quite interesting that it's using
Code:
# alsa_amixer sset Headphone 31
I had a quick look (via BTEP) and found the names of the devices:
Master
Headphone
Speaker
Side Tone (NB. my previous research suggests playing with this will create echos in phonecalls -- so probably don't play with it!)
There are a bunch of others; I got the list via
Code:
# alsa_amixer | grep '^Simple mixer'
I am slightly wary of this solution, however, since it sounds like it keeps executing these "sset" commands on a regular basis (every second or so) and it doesn't seem like that elegant a solution. I'll stick with Voodoo for now, and if it isn't enough, I'll revisit this modification of the ALSA settings.
I'll pay special attention to the warmth of the sound, too, as I've installed the CyanogenMod DSP Manager, so thanks for the tip MistahBungle
Deleted 10 char
B3311 said:
Does that fix work on MIUI ROMs?
OP says he's running that, fix says for AOSP ROMs.
Click to expand...
Click to collapse
Yeah it will; MIUI is AOSP, as is CyanogenMod (which MIUI is based upon).
Ahri said:
Yeah it will; MIUI is AOSP, as is CyanogenMod (which MIUI is based upon).
Click to expand...
Click to collapse
As I found out after clicking on link
Apologies - I'm stupid today - bloody toothache
Yea the volume is way to low. I would love a fix. No programs
There is no fix without a program. That little app of Yahyoh's doesn't work with ICS, Voodoo Louder will give you up to 6dB extra volume with headphones/headset.
Does this increase system volume also?
would like to know this as well
the sgs2 just becomes picker with headphones - you gotta go with low impedance models. something like < 20ohms
truly a handheld, fantastic ..... very very fast ... comparing it with s2 I have to say which is better.! One big problem; headphone volume is very low, the speaker is perfect. Can anyone help me, thanks
Huawei P1 Low Volume
I felt the same with you, the volume should be louder. Anyone has a solution?
I have the same issue. Even I usually listen to the music via BT headset,in the car I connect P1 with the car radio through 3,5mm jack and output definitely needs to be louder. If there is no way,how to fix it in ,then we have to wait for the new firmware I guess.
sperman2005 said:
truly a handheld, fantastic ..... very very fast ... comparing it with s2 I have to say which is better.! One big problem; headphone volume is very low, the speaker is perfect. Can anyone help me, thanks
Click to expand...
Click to collapse
I found the same problem. Can anyone help?
Use Volume+ (NEEDS ROOT)
Sent from a 2.8 inch screen
Ascend P1 low volume solution
This is a trick I figured out on my Huawei U8100 to boost volume that also works on the Ascend P1 (U9200). The effect is not huge but I guarantee you it works. This works explosively huge on the U8100, but Huawei seems to have "fixed" it partly on their new phones.
- Turn off/quit all music players, then start the FM radio.
- Click the "power" button to activate the FM tuner, then use the volume buttons to turn the volume *all the way down*. Not kidding.
- Press the home button and start your music player as usual. Adjust volume to maximum (the FM volume is maintained separately, so the tuner will remain quiet).
You can go back to the FM app and turn it on/off to see the effect. The difference is small on Ascend P1 but gives audio more punch and quality. The FM app will remember its volume setting when you start it next time. Running the FM app can also fix the problem of audio cutting out or quality going bad if you're not using the stock 4-contact headset.
In combination with this I use the latest version of Volume+ (I downloaded free version from the developer's web site). This version of Volume+ does *not* need root. Don't crank it too high because this can cause distortion. Use the EQ for best results, see image for my settings.
This app uses the Android EQ API available since Android 2.3. The Ascend P1 unfortunately has known problems with stereo imaging, which is the reason a bit of Stereo Widening in Volume+ helps.
Georg
PS: The FM app has a widget which makes it quicker to access to turn on/off. Lately I'm using a bit more gentle EQ, no bass boost, stereo widening = 1 for a more natural sound.
It works!
This seems crazy but it works, it´s not much more spl but it´s definetly better, anyway i bought a Fiio E3 Headphone Amp for 10 bucks in adittion to this trick and a litte bit of EQ my Ascend P1 it´s quite good
my fix
go to modaco.com p1 thread i posted fix for the low volume
Urmet77 said:
go to modaco.com p1 thread i posted fix for the low volume
Click to expand...
Click to collapse
Thanks Urmet77... your fix is for rooted devices, I rooted my device yesterday and applied your audio configuration fixes, definitely works great. It is the definitive fix for the low volume problem, but requires knowledge of rooting, linux shell, and superuser commands. The best non-root solution is still my post above.
Good thing with Ascend P1 is that you do not need to replace your phone's ROM to achieve root. In other words, you just do enough of the rooting sequence to acheive su privileges, but can stop before flashing a new recovery ROM or firmware. I also did not lose any user data or settings, although you are still strongly advised to back up.
Some pointers for those interested, keep in mind it's possible to permanently disable (brick) your phone. You are solely responsible for any mishaps.
- Rooting guide: www . androidiani . com/forum/modding-huawei-ascend-p1/279692-guida-huawei-ascend-p1-u9200-aio.html
- You'll need both ADB and fastboot drivers from the Android SDK (step 2 under "First of all").
- Test Fastboot drivers using 'fastboot devices'. My Huawei showed up as "?", this is ok.
- Links to get Clockworkmod and SU_Busybox_Package.zip are in the second post of the rooting guide.
- I had trouble using volume keys to boot into fastboot/bootloader mode, had to use the ADB command "adb reboot bootloader".
- Do just steps 1 - 9 under "How to Root".
- Then you can apply Urmet77's volume fix: www . modaco . com/topic/361718-fix-low-earphone-volume-fix-for-huawei-p1-p9200-stock-ics-403
For the last step you'll need to know how to transfer files to and from your computer to the system partition, activate su, remount /system read-write, set/restore any required file/dir permissions. Remember a wrong command can brick your phone. I reduced the volume settings somewhat by editing the .conf files to be sure distortion is minimized, my settings in all 6 .conf files under [Music] ... <headset>:
Headset Playback Volume=12
DL1 Media Playback Volume=113
This is still plenty loud, thanks Urmet77. I still use Volume+ to add a bit of EQ and stereo widening, many EQ apps on Google Play do the same thing.
Now a shameless plug... I use this phone to develop my audio apps "SoundWire" (live audio transmission / wireless headphones) and Music VU (rapidly updating level meter and spectrum widgets for any music player). Look them up on Google Play.
Georg
Headset Playback Volume=12
DL1 Media Playback Volume=113
My default is 18 and 115 but it depends on earphones i dont have any disortion and u are welcome for the fix
Has the issue been fixed in official update?
Hi there,
I'm considering buying the phone, and I was just guessing, since the original posts are quite old, whether the issue has been solved in any of the official firmware updates released so far.
Thanks in advance.
Nice, now to figure out how to do it on a U9508 ^^
Urmet77 said:
go to modaco.com p1 thread i posted fix for the low volume
Click to expand...
Click to collapse
Hi Urmet. I have read ur post on modaco however I still need to ask: can this fix be applied the same way on a stock p2? Thanks!
suswack said:
Hi Urmet. I have read ur post on modaco however I still need to ask: can this fix be applied the same way on a stock p2? Thanks!
Click to expand...
Click to collapse
grynnan said:
Nice, now to figure out how to do it on a U9508 ^^
Click to expand...
Click to collapse
Hello unfortunately both your phones uses k3v1 or/and k3v2 huaweis own chipsets so its not possible at this moment only huawei itself knows but u can try to erase codec folder it seemed to help on p6 huawei it uses also k3v2 chipset and advice next time u buy phone try to avoid huawei k3 chipset phones they have bad support from devs coz they have bootloaders locked and huawei is not willing to unlock them
Headset low-volume fix for P1 LTE
Urmet77 said:
go to modaco.com p1 thread i posted fix for the low volume
Click to expand...
Click to collapse
Hi.
Did any body find any method for fixing the headset low-volume bug in P1 LTE (U9202-L) in similar way ? I would appreciate any help.
Thanks
Jakub
So, I've found that the audio on Lineage OS and other Roms based on LOS wasn't as good as on the stock firmware. Both when it comes to mic and headphones audio.
I followed this up by comparing the "mixer_paths.xml" files from Lineage OS between the file from stock marshmallow as well as stock nougat (A2017G model) and there are quite a few missing lines in the AOSP version and some lines that just have different values. B.T.W Is the "mixer_paths.xml" the only file where you edit values which have to do with audio?
Anyway, I then used the standard mixer file from the stock Marshmallow firmware on the Lineage OS rom and although the sound is lower than with the standard mixer file from LOS the audio is noticeably better according to my ears. (This could be placebo but I doubt it. I also use the HD 598 headphones which are quite good compared to many other headphones on the market so the difference in audio quality is easier to discover).
Feel free to try this out if you are on a AOSP rom and want better audio. Steps below:
1: Make sure you're rooted and have disabled system write protection.
2: Navigate to System -> etc -> mixer_paths.xml.
3: Cut the "mixer_paths.xml" file to a backup location in case you want to go back.
4: Download either the marshmallow or the nougat file that I've provided below and rename it to "mixer_paths.xml" and paste it in the same location. System -> etc.
5: Reboot.
6: Profit? I don't know, it's up to you if you think it sounds better. Remember that with cheap earbuds you most likely won't hear a difference, at least I wouldn't.
You can try the process with either the Nougat or the Marshmallow file i uploaded. The Nougat is a little bit louder.
In case you want to go back then just copy the mixer_paths.xml file you backed up and replace the current mixer_paths.xml file in the same directory as above. Also reboot.
Edit: As @RUNNERX pointed out, make sure that the permissions are set to 644 and then reboot to make sure it's working correctly.
Download
I think we need a properly soundmod...
I tried with stock ROM (B19 A2017U) but it only affects the Normal Mode in headphones.
There's so much potential with this device... Ak4490 is a beast that needs to be released from its "cage".
As far as I can tell, the problem is that no custom rom is using the akm dac?
This is too bad, especially since regular dac sounds in my opinion much much better (and different) in aosp with the latest sound fix compared to stock normal (loudness being part of it). Still it is clearly not the akm dac.
On stock, both normal and superior mode have some kind of strange tuning, almost like there is some postprocessing even with dolby off. On aosp that seems to be gone at least.
It was mentioned previously that the mixer XML was ignored and all changes needed to be made the (ADC**?) files. This has since been patched resulting in proper use of akm DAC. The issues with the sound not being as good quality wise lies within these files, not the XML.
icenight89 said:
It was mentioned previously that the mixer XML was ignored and all changes needed to be made the (ADC**?) files. This has since been patched resulting in proper use of akm DAC. The issues with the sound not being as good quality wise lies within these files, not the XML.
Click to expand...
Click to collapse
Ok. Where would I find these files?
icenight89 said:
It was mentioned previously that the mixer XML was ignored and all changes needed to be made the (ADC**?) files. This has since been patched resulting in proper use of akm DAC. The issues with the sound not being as good quality wise lies within these files, not the XML.
Click to expand...
Click to collapse
So can anyone confirm that they got the akm dac working with headphones? (and comment on the results?)
I installed the AOSP extended 7.1.2 and then magisk zip, but it didn't seem to work, though it did play louder (and stereo on speakers).
Maybe I'll try a different rom...
cfbruck said:
So can anyone confirm that they got the akm dac working with headphones? (and comment on the results?)
I installed the AOSP extended 7.1.2 and then magisk zip, but it didn't seem to work, though it did play louder (and stereo on speakers).
Maybe I'll try a different rom...
Click to expand...
Click to collapse
I was under the impression that the headphone DAC has been working since early March. The stereo speaker fix has nothing to do with the headphone DAC.
https://forum.xda-developers.com/showpost.php?p=70971100&postcount=1041
Ok, it might just be that it sounds bad in the LOS-implementation then. Thanks to senny for exploring possibilities.
Just to give some feedback
This definitely changes the sound. Standard aosp sounded kind of raw to me, with tizzy trebles, though with a lot of detail. This makes it smoother, sounds more like it should in a way, easier to listen to.
There is some loss of information though, and soundstage a bit smaller.
(I found that if I tried to copy and replace the file it didn't work (sound not working). I had to first delete the mixer file present, then paste the other one.)
After replacing the file make sure permissions are 644 and reboot.
cfbruck said:
Just to give some feedback
This definitely changes the sound. Standard aosp sounded kind of raw to me, with tizzy trebles, though with a lot of detail. This makes it smoother, sounds more like it should in a way, easier to listen to.
There is some loss of information though, and soundstage a bit smaller.
(I found that if I tried to copy and replace the file it didn't work (sound not working). I had to first delete the mixer file present, then paste the other one.)
Click to expand...
Click to collapse
Well good to hear that more people find a difference.
when i'm looking at this: http://blog.son-video.com/en/2017/01/test-fiio-x5-iii/
I can't help but think that ZTE could have done so much more to make the experience more complete. The fiio got viper pre-installed, and digital low pass filter to play with that are actually coming straight from AKM :
"Five different 32-bit digital filter types are available: Short delay sharp roll-off and short delay slow roll-off filters have overall short delay characteristics. Sharp roll-off filter and slow roll-off filter preserve the phase difference and a new filter that has even slower roll-off character was added to these four filters. They are selectable according to the user audio and system preferences."
We've got a phone with one of the best DAC in the world, but can't do much because android by default is limited, and it seems obvious that zte don't have a lot of experience when it comes to makes audiophile device. a partenrship with fiio, cayin, or ibasso would have been terrific, especially considering that fioo and cayin have both already launch a product with an akm4490 running on android at full potential.
Maybe we can hope that some developer with at interest in audio can unlock some of the potential.
Listening some more with the mixer files I have to say it really is a big improvement, especially with the marshmallow to me.
Whatever it is that makes it better should be part of LOS. Using LOS 14.1 with the beastmode kernal and the changed mixer paths - it actually sounds pretty good.
However, for me changing the mixerpaths breaks audio functionality. I get no audio in calls, neither speaker nor headphones. I am using the sounds fix for stereo speakers 4.1, maybe that affects it.
Does it work without side effects for you senny? Whats your setup?
No mixer_paths.xml
Hi,i have marshall london phone and i'm sure i don't have mixer_paths.xml to edit,please help me to find the file responsible for editing volume output values.
FocaTm said:
Hi,i have marshall london phone and i'm sure i don't have mixer_paths.xml to edit,please help me to find the file responsible for editing volume output values.
Click to expand...
Click to collapse
same here I did not find the mixer_paths.xml file in my AOSP extended Android pie rom.
Install "Ainur JamesDSP v1.7" Magisk module and choose the HQ 64bit driver
Install "Audio Modification Library v.1.8.1" Magisk module
Reboot
Configure JamesDSP app
Confirmed working (speakers & headphones (can't test bluetooth)) on my FIG-LX1 (L31) - EMUI 8.0.0.148(C432) - Magisk v17.1
Edit: If you don't want ringtones/notification-sounds to be processed, switch DSP registration from global to conventional. (3dot menu - top right, screenshot added)
Huge thanks to natanrosenfeld (he made a YT video, explaining a fix for previous version (now fixed with v1.7)) - and especially the JamesDSP dev team!
Great news I seen it on .android-hilfe.de myself
Messing around and cant seem to get it right, either too loud or doesnt work
Viper4android was much easier to setup, using Huawei DTS.irs or srs_2_1.irs then not much else and worked great
redultra82 said:
Great news I seen it on .android-hilfe.de myself
Messing around and cant seem to get it right, either too loud or doesnt work
Viper4android was much easier to setup, using Huawei DTS.irs or srs_2_1.irs then not much else and worked great
Click to expand...
Click to collapse
Have you tried using the same impulse response files with JamesDSP?
Copy the .irs (or .wav, .flac) to /storage/emulated/0/JamesDSP/Convolver and enable Convolver in JamesDSP.
Works great here.
Greetings from "androphil"
callmeWhiskers said:
Have you tried using the same impulse response files with JamesDSP?
Copy the .irs (or .wav, .flac) to /storage/emulated/0/JamesDSP/Convolver and enable Convolver in JamesDSP.
Works great here.
Greetings from "androphil"
Click to expand...
Click to collapse
I did thanks
Can you send screenshot of what you have, not sure on other settings
redultra82 said:
(...)Can you send screenshot of what you have, not sure on other settings
Click to expand...
Click to collapse
Even if we'd share the exact same setup (e.g. settings/IR xy sound great with my Shure SE425 in-ear headphones, but not so great with my AKG Q701) and preference of music, it would still be incredibly subjective and mainly based on taste. Certified sound-engineers would probably disagree, I guess
My suggestion is: leave every (other) option off, download a pack of different IRs (e.g. https://forum.xda-developers.com/zenfone2/general/collection-convolver-samples-389-t3140299) and try each one out. If you found one you like, (slightly) tune it with the EQ. At least that's my "non-pro" approach.
Mostly all I want is to make the phone louder, well the phone speaker, on Bluetooth speakers etc it's fairly OK
Next issue is echo sound on ringtone and notification
I'll try IRS out and maybe someday have Viper4android
It's a system-wide audio-mod, so yes, if you have e.g. Virtual Room Effect turned on or use a noticably "reverberating" impulse response file, you'll experience echo on ringtones/notification-sounds too.
I've managed to make the speakers slightly louder by choosing the highest IR Volume Level (30dB), but I think the device's speaker volume level/overall sound-quality is just physically limited. They are not the "best" speakers after all.
callmeWhiskers said:
It's a system-wide audio-mod, so yes, if you have e.g. Virtual Room Effect turned on or use a noticably "reverberating" impulse response file, you'll experience echo on ringtones/notification-sounds too.
I've managed to make the speakers slightly louder by choosing the highest IR Volume Level (30dB), but I think the device's speaker volume level/overall sound-quality is just physically limited. They are not the "best" speakers after all.
Click to expand...
Click to collapse
I noticed the room effect and turned it off, but just using Irs or some of them and seemed to be an echo,
Speaker is good enough, it is only a phone after all, there are small bluetooth speakers now that have great volume to help
A nice guy from the Telegram channel pointed out, that you can avoid processing system sounds (ringtones/notification) by switching DSP registration mode from global to conventional (screenshot added to OP).
YEEEES!!!! This mod is also working on Huawei P20Pro with EMUI8.1.. I just follow the same steps above. Thanks a lot man!
callmeWhiskers said:
Install "Ainur JamesDSP v1.7" Magisk module and choose the HQ 64bit driver
Install "Audio Modification Library v.1.8.1" Magisk module
Reboot
Configure JamesDSP app
Confirmed working (speakers & headphones (can't test bluetooth)) on my FIG-LX1 (L31) - EMUI 8.0.0.148(C432) - Magisk v17.1
Edit: If you don't want ringtones/notification-sounds to be processed, switch DSP registration from global to conventional. (3dot menu - top right, screenshot added)
Huge thanks to natanrosenfeld (he made a YT video, explaining a fix for previous version (now fixed with v1.7)) - and especially the JamesDSP dev team!
Click to expand...
Click to collapse
Hi do you know if I can change mixer path values without root and using adb on pc? , I'm trying to raise volume of WhatsApp calls, calls and maybe a bit of loud speaker volume but I'm trying to avoid root etc. Thanks any advice would be appreciated or a link to tutorials. I'm on psmart. Thanks again
jason13v8 said:
Hi do you know if I can change mixer path values without root and using adb on pc? , I'm trying to raise volume of WhatsApp calls, calls and maybe a bit of loud speaker volume but I'm trying to avoid root etc. Thanks any advice would be appreciated or a link to tutorials. I'm on psmart. Thanks again
Click to expand...
Click to collapse
Sorry - I'm not an expert, so don't take my word for it - but I don't think that's possible, since all these files are stored in locations, where (non root) users don't have write permissions. Even with a rooted and/or custom recovery device, I don't think it's possible to alter app-specific volumes by just changing mixer_paths.xml values.
callmeWhiskers said:
Sorry - I'm not an expert, so don't take my word for it - but I don't think that's possible, since all these files are stored in locations, where (non root) users don't have write permissions. Even with a rooted and/or custom recovery device, I don't think it's possible to alter app-specific volumes by just changing mixer_paths.xml values.
Click to expand...
Click to collapse
Sorry I know I mentioned whats app but really I just mean overall volume. With my moto g5 I was able to edit mixer path values which led to louder everything. But that was only with root as I'm new to adb. Thanks for your response
jason13v8 said:
Sorry I know I mentioned whats app but really I just mean overall volume. With my moto g5 I was able to edit mixer path values which led to louder everything. But that was only with root as I'm new to adb. Thanks for your response
Click to expand...
Click to collapse
In case your bootloader is unlocked, iirc you could theoretically fastboot flash TWRP - and use TWRP's "privileged" terminal (e.g. (mount /system), adb pull/push and edit the file(s)), and then (re)flash stock recovery again - without actually rooting the device.
Again, I'm not an expert (also didn't try it myself) and can't guarantee above mentioned procedure works, despite my inner-Sherlock-Holmes tells me, your bootloader is actually not unlocked.
callmeWhiskers said:
In case your bootloader is unlocked, iirc you could theoretically fastboot flash TWRP - and use TWRP's "privileged" terminal (e.g. (mount /system), adb pull/push and edit the file(s)), and then (re)flash stock recovery again - without actually rooting the device.
Again, I'm not an expert (also didn't try it myself) and can't guarantee above mentioned procedure works, despite my inner-Sherlock-Holmes tells me, your bootloader is actually not unlocked.
Click to expand...
Click to collapse
Yeah still locked dude, tried DC unlocker but they refunded as I'm on latest security patch and admitted there is nothing they can do right now.
Themes
I upgraded from a V35 to a V60 and an very happy with the audio quality.
However, I listen to classic rock. Now I find that either Android, LG or Verizon has limited the LG V60's volume to 75% while using plug-in headset earphones and/or plug-in earbuds.
After two months of phone calls, in person visits to Verizon and web seatching there is nothing that can be done from a user perspective, that I can find. I've tried a couple of "volume booster" apps with zero success.
I've found this limitation using LG's earbuds, every set of earbuds I own, and, with Beyerdynamic 770's (250 ohm, Note, after reading reviews, I assumed the V60 would drive those 770's w/o issue). The limitation also exists played thru a NobSound DAC.
I've seen mention of "Poweramp" in other audio related threads, used in the thread to boost output from 48khz to 192khz, which should be amazing. But there are several similarly named apps...my guess is the aforementioned app is "PowerAmp Full Version Unlocker", for $5.49. Would this help volume as well?
Is there anyway to defeat this limitation?
Even a 10% increase would be satisfactory.
What if you turn on the DAC setting in the quick-settings? I'm sure you already thought of that.
svetius said:
What if you turn on the DAC setting in the quick-settings? I'm sure you already thought of that.
Click to expand...
Click to collapse
Yes, no effect.
I'm using the Neutron Player app which has a 'use on-board device's volume control' option you could turn off & use your DAC. I did this to use my tablet with an iFi DSD nano and the next time I used the [stupid] USB C to 3.5mm dongle without the DAC, it nearly blasted my ears. So if you try it, be careful when you're not using an external DAC.
The app is a pain to setup but that's because, in part, it has so many configuration options. Think Android vs iPhone taken up several notches. Once it's setup, you'll get used to the GUI/Ux itself which I did not find intuitive. Anyway, there's a free eval. version if you wanted to check it out.
Mojo1114 said:
Yes, no effect.
Click to expand...
Click to collapse
Hmm....I know this kind of sucks, but how about an external DAC? Those usually work via USB C and can provide very loud, very clean output.
Op is using a DAC.
The limitation also exists played thru a NobSound DAC.
yep_nexus said:
I'm using the Neutron Player app which has a 'use on-board device's volume control' option you could turn off & use your DAC. I did this to use my tablet with an iFi DSD nano and the next time I used the [stupid] USB C to 3.5mm dongle without the DAC, it nearly blasted my ears. So if you try it, be careful when you're not using an external DAC.
The app is a pain to setup but that's because, in part, it has so many configuration options. Think Android vs iPhone taken up several notches. Once it's setup, you'll get used to the GUI/Ux itself which I did not find intuitive. Anyway, there's a free eval. version if you wanted to check it out.
Click to expand...
Click to collapse
Thanks. It seems an app will be the solution. And I've seen Neutron Player mentioned in other threads.
To repeat your method as I understand it: Neutron allows me to turn off the phone's volume (which will bypass the 75% limitation) and send the raw signal via Neutron to my external DAC which will ultimately control volume?
And Im a bit confused by your advice to use caution the next time I plug in my phones directly into my phone with my wired headphone's 3.5 jack? That implies the phones limits are permanently bypassed? Am I understanding you correctly?
I'm also curious over PowerAmp app as well. Not being tech savy, intuitive is a plus.
And again, many thanks for taking the time to comment!
Mojo1114 said:
To repeat your method as I understand it: Neutron allows me to turn off the phone's volume (which will bypass the 75% limitation) and send the raw signal via Neutron to my external DAC which will ultimately control volume?
Click to expand...
Click to collapse
Correct!
Mojo1114 said:
And Im a bit confused by your advice to use caution the next time I plug in my phones directly into my phone with my wired headphone's 3.5 jack? That implies the phones limits are permanently bypassed? Am I understanding you correctly?
Click to expand...
Click to collapse
Right, so Neutron has another setting (and it could be Android too, not sure), that starts the app automatically when you connect headphones. Or at least it offers to start, and you can easily accidentally tap it when it pops up. I wanted to bypass my tablet's volume when I connected my external DAC, since that has a hardwire volume control so I enabled that 'bypass device's volume' control. However, later when I went to use my tablet to watch a quick video I plugged in my every day earphones, probably tapped Neutron player unintentionally, and it started playing at max volume. On my V60 phone that probably isn't super loud, especially from what you're saying. However on my Samsung tablet it was screaming loud. It happened long enough ago that I've forgotten the exact circumstances.
Anyway, that control doesn't permanently bypass the phone's volume control. You can shut it off, and I can't say for sure if it has any affect on other apps. I only made that mistake once. Later I realized the volume in Neutron was loud enough with my DAC connected. The internal volume may well be bypassed automatically. I guess I need to listen to some music again through this rig soon to test it out. Unfortunately for both of us that won't be tonight.
Mojo1114 said:
I'm also curious over PowerAmp app as well. Not being tech savy, intuitive is a plus.
And again, many thanks for taking the time to comment!
Click to expand...
Click to collapse
I haven't used PowerAmp since it first came out in the early 2000s with the advent of MP3s. But chances are it is more intuitive than Neutron Player. I'm a professional audio engineer by trade & tech nerd, yet still get caught up in the menus and different screens all the time. If it didn't sound so good and stream DSD files right along side PCM audio, and stream my entire music collection from my NAS, I'd kick it right to the curb.
My pleasure. Hope this helps! Cheers.
Any real solution for this yet? I think it can be bypassed with root access to the build prop or the sound mixer found in system/vendor/etc.
Any rooted user care to check?
Are you saying this can be fix in build prop?? Which entry?
I'm about to root my phone. Have already BL unlock it.
hooutoo said:
Are you saying this can be fix in build prop?? Which entry?
I'm about to root my phone. Have already BL unlock it.
Click to expand...
Click to collapse
It should be in one of those two files. Most likely the sound mixer file though. I don't know exactly how the entry will look but i would guess something like "headphone volume limitations = max 75"
Change 75 to 100 save and reboot.
Again this is all just guesswork I'm not a developer and haven't rooted this particular phone yet and likely won't unless we get a custom aosp.