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
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
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.
I heard that there is a lot of confusion about installing ViPER4Android on Nougat. After searching around the web i found a way to do it ^_^ It should work on all Nougat build released until now. Last test on N4F26J
First of all unistall any previous ViPER4Android app.
Requirements:
Root
TWRP
SuperSU 2.78 or higher
BusyBox 1.24.2 or higher installed in \su\xbin
Installation:
Flash ViPER4Android_2.5.0.5_guitardedhero.zip in TWRP
Go to vendor\etc and remove/rename audio_effects.conf using any file manager with root access (ex. Root Browser)
Open ViPER4Android app and install driver (Grant root permission). (It could freeze for a few seconds, just be patient!)
Reboot
Disable MusicFX app
Reboot
Done :3
I hope this will help you
Thanks to guitardedhero for the modified zip file
EDIT: fixed google drive link
ElementalX kernel not required. Thanks for the guide.... Enjoy
Works on stock?
Sent from my Nexus 5X using Tapatalk
Magisk + V4A Add-on is how I use it flash those in twrp and then install v4a apk no editing system partition and you can install ota updates then just boot twrp and flash magisk again
I want to know if its working system wide.
viper4android saying not enable and not processing....anyone with the same issue?
for me its only working in compatible mode.. anyone else?
Did not completely work for me. At first when i did the procedure everything was ok,driver installed neon,ok. But when i played native audio or pandora no difference. Also when i plugged in my Fiio K1 DAC it change to not supported abnormal. Tried clean installing into system 3x, edidtin,deleting, the file in vendor. No luck, maybe we just have to wait a bit longer, rom used is Purenexus. Also when i did it,i already had the drive installed.....
---------- Post added at 07:23 PM ---------- Previous post was at 06:51 PM ----------
UPDATE:
So i did get it working, but i used the Viper 6.01 that guitar user posted in the nexus 5x forum.
Works with only Headphone jack,
NOT with usb out. When using USB out it just dosent work.
Also for some reason my pandora now keeps crashing
BUT IT WORKS, so i think ill keep it. Ill leave the DAC/AMP at home for my laptop, and use the viper limiter at maximum and just up the bass a bit.
All i wanted was to get the bass higher with out maximizing the volume.
Id suggest using arise, it's way better than stock Viper
If I may make a suggestion that will ultimately save you a lot of grief, move to the updated ARISE sound mod by guitardedhero and others. The latest is deuteronomy 2.x and, as opposed to the tweaks, futzing and issues of sound being processed/sticking or not, this is a much simpler install and just works.
Head over to http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709 and just install the base version. You'll get Viper4ARISE. I still flash a permissive kernel zip with my Nougat ROMs, but since I switched to ARISE, V4A has worked flawlessly, and it sounds even better than the old V4A from this thread.
It also removes MusicFX with the install process and I haven't had to disable/remove the audio_effects.conf file either.
Lastly, I'm not sure development is continuing on the base V4A anyway. ARISE is the way to modify your Android sound processing now.
---------- Post added at 09:12 AM ---------- Previous post was at 09:12 AM ----------
banccalif said:
Id suggest using arise, it's way better than stock Viper
Click to expand...
Click to collapse
Sorry, only noticed your post after I posted my longer response saying the same thing
ultyrunner said:
If I may make a suggestion that will ultimately save you a lot of grief, move to the updated ARISE sound mod by guitardedhero and others. The latest is deuteronomy 2.x and, as opposed to the tweaks, futzing and issues of sound being processed/sticking or not, this is a much simpler install and just works.
Head over to http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709 and just install the base version. You'll get Viper4ARISE. I still flash a permissive kernel zip with my Nougat ROMs, but since I switched to ARISE, V4A has worked flawlessly, and it sounds even better than the old V4A from this thread.
It also removes MusicFX with the install process and I haven't had to disable/remove the audio_effects.conf file either.
Lastly, I'm not sure development is continuing on the base V4A anyway. ARISE is the way to modify your Android sound processing now.
---------- Post added at 09:12 AM ---------- Previous post was at 09:12 AM ----------
I amd a bit confused. So i still need to flash a kernel zip besides the ARISE file? I am on 7.1.1 preview with stock kernel
Click to expand...
Click to collapse
angle409 said:
ultyrunner said:
If I may make a suggestion that will ultimately save you a lot of grief, move to the updated ARISE sound mod by guitardedhero and others. The latest is deuteronomy 2.x and, as opposed to the tweaks, futzing and issues of sound being processed/sticking or not, this is a much simpler install and just works.
Head over to http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709 and just install the base version. You'll get Viper4ARISE. I still flash a permissive kernel zip with my Nougat ROMs, but since I switched to ARISE, V4A has worked flawlessly, and it sounds even better than the old V4A from this thread.
It also removes MusicFX with the install process and I haven't had to disable/remove the audio_effects.conf file either.
Lastly, I'm not sure development is continuing on the base V4A anyway. ARISE is the way to modify your Android sound processing now.
---------- Post added at 09:12 AM ---------- Previous post was at 09:12 AM ----------
I amd a bit confused. So i still need to flash a kernel zip besides the ARISE file? I am on 7.1.1 preview with stock kernel
Click to expand...
Click to collapse
You don't need to AFAIK and it isn't a kernel. V4A used to need SELinux permissive to run, but stock and most custom kernels run enforcing. I just mentioned that I flash a permissive mod out of habit FYI. You are likely better off going to the A.R.I.S.E. threads to discuss issues.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Just flashed Deuteronomy 2.1 (non classic) on my nexus 6P. After enabling V4Arise and enabling speaker optimization, the phone speaker sound is actually worse than stock, more muted across range. I haven't tried headphones yet. kinda disappointed. My advice: V4A is overhyped. just keep stock sound.
angle409 said:
Just flashed Deuteronomy 2.1 (non classic) on my nexus 6P. After enabling V4Arise and enabling speaker optimization, the phone speaker sound is actually worse than stock, more muted across range. I haven't tried headphones yet. kinda disappointed. My advice: V4A is overhyped. just keep stock sound.
Click to expand...
Click to collapse
Sorry, but you clearly haven't tested anything at all yet. Speaker optimization isn't that great and yes it mutes it, but that's to avoid the pop and tinny issues with many phone speakers. However, if you use that, then play with the EQ and other settings, you may surprise yourself. That would require more than a 5 second evaluation though.
Have you tried the EQ presets or customized them? What about dynamic sound or the various compressions? How about any number of things most people would play around with before writing something off? These types of tweaks are, after all, the point of a sound mod with a detailed EQ.
Since you admit you haven't even tried headphones, let alone bluetooth and haven't played with the EQ at all, it may just be a wee bit early to pronounce it a failure. And ... the VAST majority of people who use it would disagree.
ultyrunner said:
Sorry, but you clearly haven't tested anything at all yet. Speaker optimization isn't that great and yes it mutes it, but that's to avoid the pop and tinny issues with many phone speakers. However, if you use that, then play with the EQ and other settings, you may surprise yourself. That would require more than a 5 second evaluation though.
Have you tried the EQ presets or customized them? What about dynamic sound or the various compressions? How about any number of things most people would play around with before writing something off? These types of tweaks are, after all, the point of a sound mod with a detailed EQ.
Since you admit you haven't even tried headphones, let alone bluetooth and haven't played with the EQ at all, it may just be a wee bit early to pronounce it a failure. And ... the VAST majority of people who use it would disagree.
Click to expand...
Click to collapse
What's the point of installing it if you have to do all the work yourself in that department? I'm not an audio engineer, I don't know what is best for my phone.
siren_shadows said:
What's the point of installing it if you have to do all the work yourself in that department? I'm not an audio engineer, I don't know what is best for my phone.
Click to expand...
Click to collapse
Exactly. If regular people have to spend hours or days to tweak the settings what's the good? I wish it's the install and forget type of app.
angle409 said:
Exactly. If regular people have to spend hours or days to tweak the settings what's the good? I wish it's the install and forget type of app.
Click to expand...
Click to collapse
Worst part is I've had hearing problems since I was an infant, so like, i can't really test settings and **** since I can't really tell the difference incrementally.
angle409 said:
Exactly. If regular people have to spend hours or days to tweak the settings what's the good? I wish it's the install and forget type of app.
Click to expand...
Click to collapse
Hours or days? It takes me a few minutes of playing on a fresh install until I hit what I like. Plus, you can save your settings as a profile. However, it's clear from your responses that you can't be bothered to actually test it. If you have a home stereo, you play around with EQ until you like it. If you listen to music in your car, you set treble and bass, balance and other things. This is no different. How on earth a sound app that, at its heart is an EQ, could be set and forget BEFORE YOU INSTALL IT is beyond me. That's not even the purpose of it. If that's what you want, then you're not looking for a sound mod. The entire point of a sound mod / EQ is to allow people to adjust the sound to their preference for their hardware and listening preferences/context.
angle409 said:
Just flashed Deuteronomy 2.1 (non classic) on my nexus 6P. After enabling V4Arise and enabling speaker optimization, the phone speaker sound is actually worse than stock, more muted across range. I haven't tried headphones yet. kinda disappointed. My advice: V4A is overhyped. just keep stock sound.
Click to expand...
Click to collapse
ultyrunner said:
Sorry, but you clearly haven't tested anything at all yet. Speaker optimization isn't that great and yes it mutes it, but that's to avoid the pop and tinny issues with many phone speakers. However, if you use that, then play with the EQ and other settings, you may surprise yourself. That would require more than a 5 second evaluation though.
Have you tried the EQ presets or customized them? What about dynamic sound or the various compressions? How about any number of things most people would play around with before writing something off? These types of tweaks are, after all, the point of a sound mod with a detailed EQ.
Since you admit you haven't even tried headphones, let alone bluetooth and haven't played with the EQ at all, it may just be a wee bit early to pronounce it a failure. And ... the VAST majority of people who use it would disagree.
Click to expand...
Click to collapse
siren_shadows said:
What's the point of installing it if you have to do all the work yourself in that department? I'm not an audio engineer, I don't know what is best for my phone.
Click to expand...
Click to collapse
ultyrunner said:
Hours or days? It takes me a few minutes of playing on a fresh install until I hit what I like. Plus, you can save your settings as a profile. However, it's clear from your responses that you can't be bothered to actually test it. If you have a home stereo, you play around with EQ until you like it. If you listen to music in your car, you set treble and bass, balance and other things. This is no different. How on earth a sound app that, at its heart is an EQ, could be set and forget BEFORE YOU INSTALL IT is beyond me. That's not even the purpose of it. If that's what you want, then you're not looking for a sound mod. The entire point of a sound mod / EQ is to allow people to adjust the sound to their preference for their hardware and listening preferences/context.
Click to expand...
Click to collapse
ultyrunner is absolutely correct here. The criticisms you have leveled against this project would be considered rude (and a bit ignorant) even if you actually had a solid point to make, or some evidence to back it up. As it stands, you don't have either, and asking a question like "What's the point of installing it if you have to do all the work yourself in that department? I'm not an audio engineer..." is just unthinkable. People specifically poured blood, sweat, and tears into this thing for that exact reason... so that people who aren't engineers can improve their experience via the developer's knowledge. Either you were just being flippant about "having to do all the work yourself" and you don't actually mean that - in which case it would have been preferable for you to just say "thank you but I am having a few problems," et cetera, and be on your way...OR you do actually think you're doing all the work, which is a smack in the face to a developer... a developer whose work you very obviously do not grasp the complexity of, nor the amount of time and effort required to produce said work. Don't bash people's work if you haven't yet evaluated it properly, and most especially make an effort to understand it at a high level before you complain (if you really need to complain at all, which you don't).
I'm sorry, but if I was the developer, seeing a comment/comments like these would be enough for me to close down the project ASAP. And I'm not just pulling that out of my ass, I've been through five or six phones and development communities here on XDA, and I have seen exactly that happen on more than one occasion.
And that's the problem with XDA. People take things to personally. This isn't a forum for babies. We're allowed to express our opinions and concerns here, believe he or not.
Guide to get rid of audio distortion on CM13 and Lineage OS 14.1
I have told quite a few people in the cm13 thread how to get rid of the audio distortion, I figured it was relevant to enough people that I should make a little guide on how to set it up although it is pretty straightforward.
[Disclaimer] I am not responsible if you manage to break your phone using this guide
What does this guide accomplish? This guide will help you install Viper4Arise which is a wonderful sound mod that I use on any phone or rom. Viper4Arise will allow you to eliminate audio distortion in media playback on your Axon 7 running CM13 or LOS14.1, by lowering the output gain which is not capped properly in these Roms
What does this guide fail to accomplish? This guide will not fix mic issues, in call volume, the left channel being missing on speakers, or any other sound related problem present in CM13 or LOS14.1, however most bugs are gone now in LOS14.1
Now that that's out of the way, lets get to the fun stuff!
Step 1
First thing you want to do is grab the Viper4Arise flashable zip
Download Viper4Arise 2.3.3
however if you want the newest version
Download Viper4Arise 2.4
once you have this you can boot into TWRP and flash it, then reboot into system
Step 1.5
This step is only necessary on the newest builds of lineage OS 14.1
lineage OS does not have root built in. we will download the root addon package from lineageOS
Download root addon
flash this in twrp, it doesnt matter if it is done before or after installing the Viper4Arise package
Step 2
SeLinux must be permissive and by default it is enforcing so we are going to grab this apk and install it
Download SeLinux Switcher
once installed, open the app, allow root access (you may need to enable root in developer options) and set SeLinux to Permissive. if Viper4Arise stops working always check to make sure Selinux is still in permissive as changing it back to enforcing will stop Viper4Arise from working.
Step 3
Next we will configure Viper4Arise to eliminate Audio distortion.
Start by going to the phone speaker and Headset tabs and Switching master power to on
Now press the menu button on the top left and press Driver status. as long as SeLinux is permissive it should say
NEON Enabled: Yes
Enabled: Yes
Status: Normal
the other things are not relevant. if the above message read "No" or "Abnormal" you may not have set SeLinux to permissive, please go back to step 2!
do this twice, once with the Headset tab Selected and once with the Phone Speaker tab selected
There are allot of awesome setting to mess with they can make you audio amazing, I encourage you to try them out. to make the audio distortion go away simply scroll to the bottom and find the "Master Gate (Limiter)" tab. Set the output gain to -10.5 dB on both the Headset and Phone Speaker. this level seems pretty good in my opinion however you may find you prefer a slightly lower or higher level.
That's it! I hope I have helped you guys out, feel free to ask questions or make suggestions on how to improve this guide and be sure to leave Thanks!
Thread created: 1/31/17
Last updated: 2/2/17
This won't make audio playback through the phone speakers stereo again, would it?
Does this work for LineageOS 14.1?
Abiram26 said:
This won't make audio playback through the phone speakers stereo again, would it?
Click to expand...
Click to collapse
Nope... Sorry. I will add that to the list of things it doesn't do.
borijess said:
Does this work for LineageOS 14.1?
Click to expand...
Click to collapse
I have only tested it in CM13 as I haven't made the jump. But the audio distortion problem is the same in Lineage OS as CM13.
It will work in Lineage OS.
masong397 said:
I have only tested it in CM13 as I haven't made the jump. But the audio distortion problem is the same in Lineage OS as CM13.
It will work in Lineage OS.
Click to expand...
Click to collapse
Nice job worked on LineageOS 14.1.
Thanks for the guide. My YouTube videos are no longer distorted and sound good enough, for not having stereo capability on LOS. However, all of my notifications that come in are still very distorted, is there a fix for this?
cms062407 said:
Thanks for the guide. My YouTube videos are no longer distorted and sound good enough, for not having stereo capability on LOS. However, all of my notifications that come in are still very distorted, is there a fix for this?
Click to expand...
Click to collapse
Glad the guide helped you! Unfortunately I don't know how to get rid of distortion when notifications come in. I do believe Unjustified Dev said that all audio distortion will be gone in the near future, of course this guide won't be important at that point. At least audio quality isn't really important for notifications...
Alrighty, no big deal. You're right, it isn't a huge problem...Just a little annoying. I may have to flash back to stock, the main reason most people bought this phone was for the speakers....And I'm starting to miss the immersive sound that I had from stock
cms062407 said:
Alrighty, no big deal. You're right, it isn't a huge problem...Just a little annoying. I may have to flash back to stock, the main reason most people bought this phone was for the speakers....And I'm starting to miss the immersive sound that I had from stock
Click to expand...
Click to collapse
Yeah the left and right channel bug really degrades the speaker experience... And weird sounding notifications is annoying. I listen to lots of music but always with headphones or with an aux in the car so I don't really care too much...
Hijacking this thread to ask specifically. I do not care about my speakers I literally only use Headphones.
Is media with headphones played via the AK DAC? Is the quality as good as "super" mode on the stock ROM ? (Again, asking for Media Playback with headphones!)
Question, is the audio on LOS 14.1 with speakers good enough to listen to podcasts and some music with this mod?
Doesnt work anymore on LineageOS 14.1 latest version. I cant change back to permissive.
borijess said:
Doesnt work anymore on LineageOS 14.1 latest version. I cant change back to permissive.
Click to expand...
Click to collapse
Flashing the latest build right now. I will let you know how it goes
borijess said:
Doesnt work anymore on LineageOS 14.1 latest version. I cant change back to permissive.
Click to expand...
Click to collapse
You need root to use SeLinux mode changer. check the OP I updated how to get root.
masong397 said:
You need root to use SeLinux mode changer. check the OP I updated how to get root.
Click to expand...
Click to collapse
My fault.
I didn't realize I lost root after I dirty flashed.
iNaruX said:
Hijacking this thread to ask specifically. I do not care about my speakers I literally only use Headphones.
Is media with headphones played via the AK DAC? Is the quality as good as "super" mode on the stock ROM ? (Again, asking for Media Playback with headphones!)
Click to expand...
Click to collapse
I use headphones all the time. I love it. If you are worried about the quality compared to stock I believe you will not be disappointed. Of course I am not an audio expert and do not have the means to compare the quality side by side. I am not sure if the HiFi DAC is used, that is more of a general lineage os question.
borijess said:
My fault.
I didn't realize I lost root after I dirty flashed.
Click to expand...
Click to collapse
I just flashed SuperSU again now I have root again.
spacemanvt said:
Question, is the audio on LOS 14.1 with speakers good enough to listen to podcasts and some music with this mod?
Click to expand...
Click to collapse
The speakers are not as good as stock, the mod works perfectly but I believe only right channel is played. Its a problem that the lineage os devs have to fix. It is good for listening to pretty Mich anything, oy won't have distortion or anything
spacemanvt said:
Question, is the audio on LOS 14.1 with speakers good enough to listen to podcasts and some music with this mod?
Click to expand...
Click to collapse
Yes works great for podcasts.
This mod enables the Earpiece speaker to be used at the same time with the main rear speaker when using listening to music, and watching videos etc...
Updated
Now TRUE STEREO with Earpiece playing the LEFT channel and rear speaker playing the RIGHT channel. Test with app of your choice.
Click to expand...
Click to collapse
To install open the zip file and extract the "default_gain.conf" file and copy it to "/system/etc/default_gain.conf" using your preferred method.
Then set permissions to rw-r-r or 0644 ( e.g "chmod 0644 /system/etc/default_gain.conf" ) and REBOOT your device.
Volume levels are pushed to maximum possible without distortion with EQ on Earpiece speaker to remove low frequencies. Good luck.
Works on my SM-910K running MarshMallow 6.0.1.
WARNING!!!
THIS HAS ONLY BEEN TESTED ON THE DEVICE MENTIONED ABOVE. MAKE SURE TO BACKUP YOUR DEFAULT "default_gain.conf" FILE BEFORE INSTALLING THE NEW ONE.
(E.g "adb pull /system/etc/default_gain.conf [safe location here]" or "adb shell cp /system/etc/default_gain.conf /sdcard/default_gain.conf.bak" )
To be SAFE DO a NANDroid backup in Recovery.
Happy modding.
NOTE:
If you cannot find "/system/etc/default_gain.conf" file on your device then this MOD will NOT WORK for you. If that is the case you can try the other surround mods for other variants of the Note 4. This has only been tested to work on the N910K.
I created this one because the mods for the other variants didn't work on my phone since it uses the "default_gain.conf" file instead of the 'normal' "mixer_paths.xml" file.
Source
https://github.com/salvenose/dual_mod
Changelog
v1 -> Initial Dual Speaker Mod
v2 -> Upgrade to true stereo
v3 -> Fix for audio leak through earpiece while Headphone connected
Tried it on my N910F running 6.0.1 and seems like it works,but need to cover the main speaker to hear anything from the earpiece.
alexetna95 said:
Tried it on my N910F running 6.0.1 and seems like it works,but need to cover the main speaker to hear anything from the earpiece.
Click to expand...
Click to collapse
If there was a quick ON/OFF toggle you would notice that it makes quite a difference than with it turned off completely. Especially when you receive a notification etc... with your phone lying on a flat surface.
I haven't yet figured out how to manipulate the EQ settings for the front earpiece so that it only outputs mid-treble range without any bass.
Once I do, I'll be able to boost the volume without causing distortion. Otherwise it might damage the earpiece.
Where shoud I found that toogle ?
Actually I didn't find a "default_gain.conf" file in etc,so I just simply copied the one from your mod zip.
alexetna95 said:
Where shoud I found that toogle ?
Actually I didn't find a "default_gain.conf" file in etc,so I just simply copied the one from your mod zip.
Click to expand...
Click to collapse
If you didn't find a "default_gain.conf" file then the mod definitely won't work. It's not working for you.
Would this work on N910U?
It works on the 910C running Nemesis
Good job OP, this mod on 910C it is been hit and miss with a lot of distortion. This is the best implementation I have used. ?
Finaly N910c has this mod
It is working. Thank you very much :highfive::highfive:
Came from @mangui's post in NEMESIS REFINED V3.8.5 N7 Port by*ananjaser1211
Confirmed!!! This work good on 910C , thanks very good mod
Working, but after first call - microphone stop working
Fixed call microphone
alextalexus said:
Working, but after first call - microphone stop working
Click to expand...
Click to collapse
I've fixed it ?
Hi theres a bug
when I plug in earphones , sound still comes out of front mic
Here is the source pushed to GitHub
https://github.com/salvenose/dual_mod
Possible Fix
Ryuce said:
Hi theres a bug
when I plug in earphones , sound still comes out of front mic
Click to expand...
Click to collapse
Can you tell me if this fix works
https://raw.githubusercontent.com/salvenose/dual_mod/master/default_gain.conf
sVenose said:
Can you tell me if this fix works
https://raw.githubusercontent.com/salvenose/dual_mod/master/default_gain.conf
Click to expand...
Click to collapse
Thanks bro its fixed!
Ryuce said:
Thanks bro its fixed!
Click to expand...
Click to collapse
Alright. Just added v3 to the original post. Have a nice day and God bless you.
Wooooow
Thats awesome
V3 Working great on N910C ,
I found another bug
When i make phone call people i call cant hear me
Ryuce said:
I found another bug
When i make phone call people i call cant hear me
Click to expand...
Click to collapse
Yes i have the same problem,
I have to restart my phone, then it worka fine
Hi again,
After update to erobotrom v1.2, I have the same problem - microphone stop working. Somebody have the original mixer_path and default_gain or the other solution for this problem. Thx.