Related
Hello I'm having a problem, I need to edit AudioService.class to gain more volume in my Xperia J (it's limited by design...stupid EU law). The framework.jar is not as usual, it's an .odex file in the phone which means I had to unpack the contents of it first.
But after using this tool http://code.google.com/p/smali/wiki/DeodexInstructions All the files lost it's structure and I can't even modify the audio values right now.
Also is it possible to odex deodexed files again to make them work on stock rom (based on ICS)?
I've tried to send this message to sony but their forum is dead so here it is explained furthermore:
Hello, I'm furious with my new phone. The headphones volume is not sufficient at all (I'm talking various models of HEADphones, not earphones, although the standard ones that come with the phone are not loud enough to me as well).
The sound also appears compressed on this model which for example means that if something is played at low volume for longer period of time the phone automatically levels the sound to be louder and if something strucks like an explosion for example the sound reduces to the limited value that to me sounds lik 85dB and the phone can handle a lot more beacause when someone calls me while I'm listening to music, music just BOOOMS up the volume for a second and then the ringtone comes in. I had the same issue with my HTC phone but Volume+ app from market could fix that, however on Xperia J with ICS on board none of the volume hacking applications work.
Click to expand...
Click to collapse
Can anyone please help?
Here are the both files (the original thread where I found how to increase volume on other Xperia phones): http://forum.xda-developers.com/showthread.php?t=2080773&page=5
Hello,
This is my personal edit of the mixer_ paths.xml for the G4 [H815] to increase the headphone volume and decided to share it.
You might say, that there is already a thread for this, but unfortunately none of the files provided there did the trick and the volume remained the same as before - on Android 6.
As the FauxSound module was giving me issues (muffled sound each time I inserted the headphones), so I decided to dig deeper and modify the the file as it was working on my previous devices and finally managed to get it work.
The testing method was the following:
Used 4 tracks (HQ sync via Deezer App) and the same headphones (Ultimate Ears super.fi 3) and comparing them before and after
1. Armin Van Buuren - Waiting for the night
2. Sebastian Brandt - Mana
3. AC/DC - TNT
4. Eagles - Hotel California
With the default mixer_paths.xml tracks 1. and 2. were playing loud enough at MAX volume, but 3. and 4. were much quieter
After modifying the mixer_paths.xml tracks 1. and 2. were playing very loud with distortions appearing at MAX, but 3. and 4. were now loud enough.
After experimenting I decided to go with digital RX values "90" as with this setting I had all of my tracks playing loud enough for my needs and much louder than the default setup, but if it is too loud or not enough for you, feel free to modify it.
INSTALLATION:
1. download the attached .zip and extract it
2. navigate to system/etc and backup your original mixer_paths or rename it to mixer_paths.xml.bak (use e.g. Root explorer)
3. copy over attached file
4. set permissions 0644 (or rw-r--r--)
5. reboot
Make sure you have granted root access and mounted /system as RW.
Tested on the H815 INT variant only and Android 6.0 (V20c and V20d)
*it should work on V20e as well, as it is basically same as V20d
*it probably will not work on other variants if the file location/name or the contents are different
add speaker too if you can!!!
pikachukaki said:
add speaker too if you can!!!
Click to expand...
Click to collapse
Speaker is also set to 90 from 84.
Will give it a try and thanx for the mod..
It works in my G4 (20d). Thank you very much for your work
Can you make a flashable zip? I'm having a lot of problems, i've moved the file of the mixer to the etc folder but the volume is the same
I deliberately didn't provide any files, as between country/region/version differences I didn't want to have any problems caused in the off chance that something was different.
I provided a very clear step-by-step that took 5 minutes tops to do, yet people still complained about lack of zips or the whole file itself? I thought XDA was about learning how to modify your device, power users and all.
As for the files other people provided, I cannot speak for them working or not. Again, with the mod being ridiculously simple, I didn't test them myself.
If there's differences in the files between LP and MM, I'd would ask you to provided the details on which lines you changed in order to replicate your mod if someone doesn't want to use the provided file?
Anyhow, I'm glad to see other people experimenting on it in general. Maybe there's a magic value that makes it sound better, though I've not been able to find it!
Cheers
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.
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