Related
As most of you know, alankila published a modified AudioFlinger library that gives rooted Android installations much-needed DSP capabilities. (See here.) This has been upstreamed to Cyanogen-6 development branch and has been released in CM6 stable and a few other cooked ROMs. However, there wasn't much information on installing it on stock ROMs with locked bootloaders/recovery images (i.e. will only accept Google-signed update ZIPs), so here's a tutorial on how to do that. This has been tested working on my Nexus One running FRF91 and the stock HTC Passion bootloader and recovery image.
NOTE. You must be root!
1) Download the attached dsp-signed update ZIP. I'm not sure which version this is, but it lets you control both the speaker and headset curves independently.
2) Extract its contents to a local folder or to the SD card on the phone.
3) Using ADB, drop to a root shell (adb shell, then su.) and remount the system partition as read-write.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Afterwards, make a backup of libaudioflinger so that you can restore it in case your phone blows up.
Code:
mv /system/lib/libaudioflinger.so /system/lib/libaudioflinger_bak.so
. Finally, copy DSPManager.apk to /system/app and the modified libaudioflinger on your SD card to /system/lib.
Code:
mv [path-to-files]/DSPManager.apk /system/app/
Code:
mv [path-to-files]/libaudioflinger.so /system/lib/
4) Reboot.
If your phone fails to boot, just delete the libaudioflinger library you copied over and restore the original from the backup you made.
Enjoy! It's fantastic!
This works great on my Incredible with stock 2.2!
Thanks!
Of course, you could also just install ROM Manager, then flash a custom recovery image and install the update ZIP that way if it's easier.
Does this app control ear piece, speaker and headphones? also does it apply the settings to calls as well as music? thanks. I have it on my phone for evils sense rom but not really noticing much of a difference. thanks.
This works great, I just wish the sliders were a bit more responsive.
installed through clockwork recovery on LeoFroyo rom 2.0.1Beta3, and it works like a charm. the sliders could use + and - icons on side to help change the numbers.
All the dsp settings do is make my speakers clip...
Sent from my Nexus One using XDA App
I would be careful with equalizing the speaker; if it's like most phone speakers, it's pretty fragile...
@jdub: It works for speakers, headphones and bluetooth devices. It affects all sound on the phone.
dgart08 said:
All the dsp settings do is make my speakers clip...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Same here, no matter how slightly (0.3dB or so) I change the level of any band, it clips when connected to my car stereo, with headphones the issue is also present but less annoying.
will this work for bluetooth streaming
danimar1 said:
Same here, no matter how slightly (0.3dB or so) I change the level of any band, it clips when connected to my car stereo, with headphones the issue is also present but less annoying.
Click to expand...
Click to collapse
I found if you have your Nexus connected to your car stereo, the speakers will not clip if you turn the headset volume down one or two notches below 100%.
GchildT said:
I found if you have your Nexus connected to your car stereo, the speakers will not clip if you turn the headset volume down one or two notches below 100%.
Click to expand...
Click to collapse
I think I already tried that, but I'm not totally sure though ... I will flash it again and give it a try. Thanks for the tip!
can this be installed on miui as per the OP?
mtw4991 said:
can this be installed on miui as per the OP?
Click to expand...
Click to collapse
The framework etc. in MIUI is not compatible with this mod. will cause bootloops... But if you find a solution please share, I'm really missing the DSP Manager and Trackball Alerts in succession on the MIUI Rom!!
cyberspaced said:
The framework etc. in MIUI is not compatible with this mod. will cause bootloops... But if you find a solution please share, I'm really missing the DSP Manager and Trackball Alerts in succession on the MIUI Rom!!
Click to expand...
Click to collapse
I am running DSPManager v1.0 on my N1 using Rodriquez v1.1 ROM. I actually used Titanium Backup to install from a backup. The apk is in my /data/app folder. APK is listed as com.bel.android.dspmanager-1.apk
Docmjldds said:
I am running DSPManager v1.0 on my N1 using Rodriquez v1.1 ROM. I actually used Titanium Backup to install from a backup. The apk is in my /data/app folder. APK is listed as com.bel.android.dspmanager-1.apk
Click to expand...
Click to collapse
Yes, you can install and run the app, but i doubt it will actually do anything, might also be the reason Rodriguez removed the app from his ROM....
cyberspaced said:
Yes, you can install and run the app, but i doubt it will actually do anything, might also be the reason Rodriguez removed the app from his ROM....
Click to expand...
Click to collapse
I could have sworn on his first version I did hear a difference. Just checked with v1.1 and you're right. Nada. My bad....but appreciate the reply.
droid x 2.2 fails to boot, stuck on motorola logo.
someone *please* make this work!
To preven cliping enable audicompression to lowest level. Works for me
I badly want to try the DSP manager. Can I use this with my rooted vibrant running stock android 2.1?
This Guide helps on configuring the A.R.I.S.E. (Auditory Research in Sound Enhancement) Sound System, including Viper4ARISE, in your Axon 7. This fixes the low volume problem for the EU version of AXON 7 2017G and increases the quality in all the models. Among other features it reconstruct the signal for streaming audio, increasing the spectrum and bringing more detail to the sound. It is also compatible with Dolby ATMOS. The official thread is complicated since it offers a lot of different options. Here I try to provide an easy and straightforward guide for beginners. After a while you will be able to get into the universe of profiles, settings and extras explained in the official thread.
REQUIREMENTS:
- Since this package modifies your system partition, it requires unlocked bootloader and root.
- Another requirement is to have the Busybox patch. If your root method is not including it, just grab one of the many free Busybox Apps from Play Store.
WARNINGS:
- Since this module is not systemless, in case of an OTA upgrade you will need to reflash the stock system before performing an OTA upgrade, apply the upgrade and then reinstall the Sound System.
- Unfortunately there is no uninstaller so keep a backup of your system partition before proceeding with the installation.
DOWNLOADS:
For a safe installation begin using ARISE Deuteronomy 2.2.3 Patched. Some people likes better the sound athmosphere provide by this version. The latest stable release ARISE Deuteronomy 2.3.3 and other versions can be found in the official thread. However 2.2.3 patched has proven to be very stable and fully compatible with our device. Later on you can test upgrading to the current or another release.
Since ARISE Sound Systems rewrites the audio configuration depending on your settings, you may need the Dolby ATMOS add-on too to recover this feature.
You'll have to flash it using TWRP recovery 3.0.3 or Flashfire app.
INSTALLATION:
STEP 0: Ensure you have a backup of your system partition and you have downloaded the ARISE Sound System to the internal or external storage of your phone.
STEP 1: Disable Dolby ATMOS.
STEP 2: Flash ARISE Sound System version 2.2.3 patched either using TWRP or Flashfire.
STEP 3: Reboot, play some music, open Viper4ARISE, activate the master switch for your headset and enjoy. Save your current configuration in the hamburger menu before testing new settings. You can also tune the phone speakers, bluetooth and external USB DAC settings.
STEP 4 (Optional): If Dolby ATMOS is not working after applying the patch, Flash the Dolby ATMOS add-on.
TROUBLESHOOTING:
- If ask for driver installation then Open your favorite file explorer and go to: /vendor/etc and rename audio_effects.conf to audio_effects.conf.bak, reboot and follow step 3 again.
- Ensure you have unlocked the system partition by typing reboot disemmcwp in the system or TWRP terminal or ADB shell. and repeat from step 1.
MY SETTINGS:
My recommendation is to leave Dolby ATMOS disabled unless you are watching a movie or concert. You do not have to disable Viper4ARISE when using Dolby ATMOS, however do never mix surround or spatial processing in both, it will be a mess. I share my general settings as an starting point, however you can experiment with all the parameters to find the sweet spot for your gear. Do not forget to save your current configuration in the hamburger menu before testing new settings, it is hard to remember the detailed configuration afterwards:
Check that the Headset HiFi setting in your Phone settings is set to Super. and for Viper4Arise set:
Master Power ON
Spectrum Extension ON (only for low quality streaming)
- Strength: 0.2
Dynamic System ON (Headset Only)
- Listening Device: Common Earphone v2
- Dynamic Bass: 18% for acoustic music and high dynamic range sources, up to 29% when listening dance/electronic
ViPER Bass OFF (only activate it if your headphones require extra Bass. In my case I have it disabled).
- Bass Mode: Natural
- Bass Frequency: 40hz
- Bass Boost: 13dB
VIPER Clarity ON (It can bring up pretty good detail to the sound).
- Clarity Mode: Natural
- Clarity: 6dB
Master Gate (Limiter)
- Channel Pan:0%
- Output Gain: 2.3dB (set more if you want more output volume without making quantization noise audible)
- Limit Threshold: 0dB
After setting it, just toggle the master switch several times to hear the difference. You will realize how much quality can be extracted from this excellent Axon 7 hardware.
How was your experience?
I love this mod, but every once in a while (like at least once or twice a day) I have to disable/ re-enable V4a or restart my phone because something goes wrong with it and it turns off (but shows it's on), like the driver unloads? So, I came back to the stock Dolby Atmos.
Hello, I'm having issues having viper to download drivers, for some reason, I am unable to rename audio_effects.conf with either es file explorer or root explorer despite es file explorer saying renamed successfully but it wouldn't change or show after reboot. I made sure they both have root permission. I have also checked if I have busybox installed but it came with systemless root. Root Switch shows selinux is set to permissive. So i'm scratching my head trying to figure out what the issue is.
PS. forgot to mention my bootloader is also unlocked.
vyurdin said:
Hello, I'm having issues having viper to download drivers, for some reason, I am unable to rename audio_effects.conf with either es file explorer or root explorer despite es file explorer saying renamed successfully but it wouldn't change or show after reboot. I made sure they both have root permission. I have also checked if I have busybox installed but it came with systemless root. Root Switch shows selinux is set to permissive. So i'm scratching my head trying to figure out what the issue is.
PS. forgot to mention my bootloader is also unlocked.
Click to expand...
Click to collapse
Did you ever do a "reboot disemmcwp"?
If not, turn on usb debugging, connect the phone to your computer and do a "adb reboot disemmcwp".
This disables the write protection on /system.
Loader009 said:
Did you ever do a "reboot disemmcwp"?
If not, turn on usb debugging, connect the phone to your computer and do a "adb reboot disemmcwp".
This disables the write protection on /system.
Click to expand...
Click to collapse
It works now, thanks! luckily I didn't have to edit that file.
Did anyone get it to work on Cm13? For me the driver fails to load with status abnormal, both with stable and alpha of Deuteronomy
nupi said:
Did anyone get it to work on Cm13? For me the driver fails to load with status abnormal, both with stable and alpha of Deuteronomy
Click to expand...
Click to collapse
Change the Selinux to Permissive on boot.
reV17 said:
Change the Selinux to Permissive on boot.
Click to expand...
Click to collapse
I shall try that. Can I put it back to enforcing after boot? I really dislike running devices on permissive...
nupi said:
I shall try that. Can I put it back to enforcing after boot? I really dislike running devices on permissive...
Click to expand...
Click to collapse
Unfortunately I don't believe it'll work if you put it back to enforcing.
tele_jas said:
I love this mod, but every once in a while (like at least once or twice a day) I have to disable/ re-enable V4a or restart my phone because something goes wrong with it and it turns off (but shows it's on), like the driver unloads? So, I came back to the stock Dolby Atmos.
Click to expand...
Click to collapse
Dolby ATMOS is meant for movies or concerts. Music sounds horrible with Dolby ATMOS.
I have been using this mod for about a week now in this device without any issue. I have tested the three proposed versions, and I have: the bootloader unlocked, F2FS filesystem, root, Xposed (all 9 modules working) and SafetyNet below this sound system.
What ROM are you using? Have you unlocked your system partition by doing a reboot disemmcwp in the terminal or adb shell? What version of ARISE Sound Systems are you using? How did you root your phone? Perhaps we could help you on this.
nupi said:
I shall try that. Can I put it back to enforcing after boot? I really dislike running devices on permissive...
Click to expand...
Click to collapse
You can try setting up V4A in enforcing mode using this guide.
for me it doesn't work, it ask for install drivers every time i reboot, and for no reason selinux don't stay to permissive after reboot (with selinuxmodechangerv3.2).
so i have abnormal statuts in viper4arise.
i try with stock b06, stock b08 and stock b09, it never work for me (maybe is because of b09 bootstack).
i also cannot use xposed framework anymore with b09, i can install it but if i activate any mod and reboot my phone bootloop.
Killerdog said:
i also cannot use xposed framework anymore with b09, i can install it but if i activate any mod and reboot my phone bootloop.
Click to expand...
Click to collapse
Did you try xposed 87? November security patches broke the earlier versions
nupi said:
Did you try xposed 87? November security patches broke the earlier versions
Click to expand...
Click to collapse
i try updating xposed inside the app. update is ok, but if i activate any module it bootloop at next reboot.
Oki said:
Dolby ATMOS is meant for movies or concerts. Music sounds horrible with Dolby ATMOS.
I have been using this mod for about a week now in this device without any issue. I have tested the three proposed versions, and I have, the bootloader unlocked, F2FS filesystem, root, Xposed and SafetyNet below this sound system.
What ROM are you using? Have you unlocked your system partition by doing a reboot disemmcwp in the terminal or adb shell? What version of ARISE Sound Systems are you using? How did you root your phone? Perhaps we could help you on this.
Click to expand...
Click to collapse
> I used the latest 2.3.3, flashed it twice in the past month (also tried an older one, but not sure which one)? Also flashed just V4a, with the same issue
> I'm running Z.A.D. Mix7 (V.3) ROM
> Xposed is installed for status bar changes only, and re-orientated volume
> I did do the disemmcwp (had to do this for my font and emoji changes to stick)
> I was one of the few that have the actual ZTE unlocked bootloader, then I followed DrakenFX thread on how to root.
But... the reason I went to ARISE, was because I wanted to use my favorite music player, n7 music player..... Which isn't compatible with Dolby Atmos. So, the issue may have been with n7? I'm currently trying to decide between XenoAmp and Double Twist Cloud Player as my player of choice. I also used PowerAmp for about 4 years, even ran the beta (build 703) up until about 3 months ago, but am tired of the same Gingerbread style UI it's had for the past 3 or 4 years.
So, that's where I'm at.... I may try it again without n7?
Killerdog said:
for me it doesn't work, it ask for install drivers every time i reboot, and for no reason selinux don't stay to permissive after reboot (with selinuxmodechangerv3.2).
so i have abnormal statuts in viper4arise.
i try with stock b06, stock b08 and stock b09, it never work for me (maybe is because of b09 bootstack).
i also cannot use xposed framework anymore with b09, i can install it but if i activate any mod and reboot my phone bootloop.
Click to expand...
Click to collapse
Try rooting your device using this method. The root includes Xposed (I have 8 modules up and running) and everything should be working. Probably using HelsAx7 as the base ROM could solve your problem.
tele_jas said:
> I used the latest 2.3.3, flashed it twice in the past month (also tried an older one, but not sure which one)? Also flashed just V4a, with the same issue
> I'm running Z.A.D. Mix7 (V.3) ROM
> Xposed is installed for status bar changes only, and re-orientated volume
> I did do the disemmcwp (had to do this for my font and emoji changes to stick)
> I was one of the few that have the actual ZTE unlocked bootloader, then I followed DrakenFX thread on how to root.
But... the reason I went to ARISE, was because I wanted to use my favorite music player, n7 music player..... Which isn't compatible with Dolby Atmos. So, the issue may have been with n7? I'm currently trying to decide between XenoAmp and Double Twist Cloud Player as my player of choice. I also used PowerAmp for about 4 years, even ran the beta (build 703) up until about 3 months ago, but am tired of the same Gingerbread style UI it's had for the past 3 or 4 years.
So, that's where I'm at.... I may try it again without n7?
Click to expand...
Click to collapse
PowerAmp and Player PRO are the best in sound quality, the second is even better. And both seem to be working fine with Viper4ARISE. What kind of source are you playing (bandwidth and bitdepth)?
This makes my music sound sweet! I don't know if anyone experienced this but my phone has 0% sleep and is always 100% awake and heats up like an oven after flashing this I restored my backup and it's okay now
Teet1 said:
This makes my music sound sweet! I don't know if anyone experienced this but my phone has 0% sleep and is always 100% awake and heats up like an oven after flashing this I restored my backup and it's okay now
Click to expand...
Click to collapse
You can use wake lock detector to check what's wrong. The package is pretty stable. Could you please provide some more info (device, ROM, root method, media player, ARISE version, Viper4A configuration...)?
Oki said:
Dolby ATMOS is meant for movies or concerts. Music sounds horrible with Dolby ATMOS.
I have been using this mod for about a week now in this device without any issue. I have tested the three proposed versions, and I have, the bootloader unlocked, F2FS filesystem, root, Xposed and SafetyNet below this sound system.
What ROM are you using? Have you unlocked your system partition by doing a reboot disemmcwp in the terminal or adb shell? What version of ARISE Sound Systems are you using? How did you root your phone? Perhaps we could help you on this.
Click to expand...
Click to collapse
I'm wondering if you can help me with another issue I'm experiencing since I last posted here. My battery started draining really fast since I flashed the audio patch, I'm aware that's normal for viper but this is abnormal since the battery drains when the phone is not in use and it tends to stay warm. I have never had this issue when I had viper on my note 4.
The steps I have done for my phone:
Root method by jcadduono’s official thread in your safety net guide with success.
Done all steps with safetynet steps from above with success.
And I did the audio upgrade from this thread with success by using your preferred one.
And that's when my phone started draining more than it usually does for viper and being slight warm when not in use. I have already done a wipe before I did all these methods.
EDIT: Someone already mentioned the issue I'm having and I did not see that on mobile. I'm running all of those on A2017U stock rom running on b29 for additional info. I used stock music player, usb audio player pro (eXtream Software Development) for external dac and Equalizer + (DJiT) which i rarely use. I'll install wakelock detecter and ill report back what I find.
Hello Everyone,
This is a collection of modules and a 1 flashable zip to enable aptX and aptx-HD on Oreo ROMs that doesn't have them...
the original files are taken from OnePlus OOS Oreo ROM, this should work (one of the options) on any OReo ROM, it may also work on N Roms but that's is not tested.
all modules flash the lib files to different places (or to all places), please the options, and select what is appropriate to you.
Bug reporting.
if you're going to report any issue please attach a log (the log should be taken before enabling Bluetooth and should record it being enabled and then being connected to an aptX enabled device)
Updated on January 6th 2018:
- 3 Magisk Modules added Description bellow for each.
- all 3 modules are based on the latest 1500 (15.0) Magisk template.
- APTX-enabler.zip is not a Magisk Module it's a recovery flashable zip, Description bellow.
should Works On All Oreo Roms.
Requirement:
-Root
-Root file manager
-Recovery (TWRP) for flashable Zip
A- Manual Installation:
1- download & extract the zip attached. ( APTX-enabler)
2- copy the files from System/vendor/lib64 folder to same place on your device, 0644 permission to both.
2- copy the files from System/lib and System/lib64/ folders to same place on your device, 0644 permission to both.
3- open build.prob in a text editor (or through the file manager) and add the following line at the end of it.
Code:
persist.bt.enableAptXHD=true
persist.service.btui.use_aptx=1
persistent.bt.a2dp_offload_cap=sbc-aptx-aptXHD
5- reboot
B- Flashable Zip Installation
1- reboot to TWRP
2- flash APTX-enabler.zip
3- reboot
C-Magisk Module
1- Download one of the 3 modules (discretion bellow)
2- install through Magisk manager
3- reboot
Modules Description:
A- aptX-HD_OreoEnablerOOS.zip , add the lib files only to System/vendor/lib64/ , some Roms like OOS Oreo Roms only require that for aptX to be enabled, it's not only for OOS other Roms use that too, if you don't know Use option C.
B- aptX-HD_OreoEnabler2.zip , add the lib files to system/lib and system/lib64 only... some roms like Nitrogen doesn't require to add any Libs on the vender folder, if not sure also use Option C.
C- aptX-HD_OreoEnabler.zip, this will add the lib files to ALL possible places, insuring that no matter what ROM you have aptX works...if you don't know which folder your ROM uses either ask the Rom Dev or use this option.
Old lib Files and modules can still be found on the following folder
https://drive.google.com/open?id=1aJQiFlzFgQmDJb08QZ_NMLUc0eKqBPry
Credits to
@Riku Azhurlar for initial flashable zip
@simonsmh for the Initial Magisk Module
@bmg1001 & @ossito2012 for initial aptx files
OnePlus for Current aptX lib files
theduke7 said:
Hello Everyone,
The latest beta of Android Oreo doesn't have AptX support like the previous bet a builds (because of compatibility Issue)
It only plays on SBC, so until OnePlus brings it back, i found a work around but it requires ROOT.
The files provided, are from a Magisk module port to Nexus 6P ...thanks to @ossito2012 for providing the file
Click to expand...
Click to collapse
I appreciate the mention but I would like to say that I did no actual work, I merely tripped over it while looking for information about aptx in the XDA Forums, this dev named @bmg1001 hooked me up with zip file.
Remember you will need aptx capable BT headphones to see it switch from SBC to aptx. I would like to say I have a picky ear but there is not much improvement over SBC going to AptX, I think because the earbuds I have are cheap. The LDAC codec is much better but the Sony headphones that have that capability are crazy priced.
ossito2012 said:
I appreciate the mention but I would like to say that I did no actual work, I merely tripped over it while looking for information about aptx in the XDA Forums, this dev named @bmg1001 hooked me up with zip file.
Remember you will need aptx capable BT headphones to see it switch from SBC to aptx. I would like to say I have a picky ear but there is not much improvement over SBC going to AptX, I think because the earbuds I have are cheap. The LDAC codec is much better but the Sony headphones that have that capability are crazy priced.
Click to expand...
Click to collapse
yes i always forget to mentioned the earbuds part... OP3 here have LDAC support , but as you said the headphones are very expensive..,
thanks for you reply, i'll the dev name to credit.
If you go into developers options under Bluetooth audio codec and enable optional codecs it turns on apt hd and ldac turns on aptx without this.
Edit: I see what you're saying now when I actually connected the Bluetooth headphones I saw you can't change those options so I'm going to use the instructions thanks.
Thanks.. It worked.. You. Are Awesome...
Last time I tried a flashable zip (Someone posted a thread) on OpenBeta 24 (Android 7.1.1) but that time flashable zip didnt worked for me... But this time doing manually worked like a charm.. Thanks man
info2shail2010 said:
Last time I tried a flashable zip (Someone posted a thread) on OpenBeta 24 (Android 7.1.1) but that time flashable zip didnt worked for me... But this time doing manually worked like a charm.. Thanks man
Click to expand...
Click to collapse
yes i tested that too, it's an old port but it has N API files, so they wouldn'e work...
i was lucky i found the Oreo files
Glad it helped
Yes.. I know.. Thats y i said i tried on openbeta 24.. OB24 was on Android N 7.1.1 and even after that didnt worked for me.. But manually doing with your zip worked for me.. Thanks again
theduke7 said:
yes i always forget to mentioned the earbuds part... OP3 here have LDAC support , but as you said the headphones are very expensive..,
thanks for you reply, i'll the dev name to credit.
Click to expand...
Click to collapse
Aptx is there if u choose enable optional codec. Look at the screenshot below. I know it shows aptx hd bt i have tried it with aptx compatible bluetooth headset and it works
The screenshot is without using any mod. Default oos oreo
jokerpappu said:
Aptx is there if u choose enable optional codec. Look at the screenshot below. I know it shows aptx hd bt i have tried it with aptx compatible bluetooth headset and it works
The screenshot is without using any mod. Default oos oreo
Click to expand...
Click to collapse
I had said the same thing until I connected my Bluetooth headphones. It won't let you change from the default codec when connected. Which is what this is a work around for.
beeree7 said:
I had said the same thing until I connected my Bluetooth headphones. It won't let you change from the default codec when connected. Which is what this is a work around for.
Click to expand...
Click to collapse
When u connect Bluetooth headset it automatically detects and uses best settings for it. When i connected my aptx enabled device it auromatically chose aptxhd. When i connected a normal Bluetooth device with no aot3x ldac it automatically chose sbc. It seems to work like that. U cant change it afterward it takes the setting automatically
jokerpappu said:
When u connect Bluetooth headset it automatically detects and uses best settings for it. When i connected my aptx enabled device it auromatically chose aptxhd. When i connected a normal Bluetooth device with no aot3x ldac it automatically chose sbc. It seems to work like that. U cant change it afterward it takes the setting automatically
Click to expand...
Click to collapse
it's not working, OnePlus disabled the codec itself , that's why when you add those files to the lib folder, they don't over right anything... there's bug reports about it
https://forums.oneplus.net/threads/open-beta-25-bluetooth-aptx-is-not-working.656630/
so OnePlus said they temporarily disabled the codec, before adding those files, download a log app and see if it enables Aptx while pairing.
and i personally assisted the OnePlus BugHunters team collecting Logs for the issue...
your theory is right, in the future it should work automatically or with forced selection, at it's current state if you play any file it defaults to SBC only (try it)
I know that this thread is specifically for those running Oreo Open Beta. However, would it be safe to flash this for those running the most up-to-date OxygenOS (4.5.1)? Please let me know if you can. Thanks.
jokerpappu said:
Aptx is there if u choose enable optional codec. Look at the screenshot below. I know it shows aptx hd bt i have tried it with aptx compatible bluetooth headset and it works
The screenshot is without using any mod. Default oos oreo
Click to expand...
Click to collapse
You need to learn a lot more... Your screenshot missing bluetooth connected icon...
sorry wrong reply, never-mind this
B4oE said:
I know that this thread is specifically for those running Oreo Open Beta. However, would it be safe to flash this for those running the most up-to-date OxygenOS (4.5.1)? Please let me know if you can. Thanks.
Click to expand...
Click to collapse
the files are Oreo specific, if you search the forums, you'll find ones for Nougat and i think there's also a magisk module
jokerpappu said:
When i connected my aptx enabled device
Click to expand...
Click to collapse
Could you reveal what's your aptx enabled device?
Flashable Zip
@theduke7 heres a flashable zip for ya. since i was bored and had nothing better to do
Riku Azhurlar said:
@theduke7 heres a flashable zip for ya. since i was bored and had nothing better to do
Click to expand...
Click to collapse
thanks m8, added to OP with credit
i want to report that it works in nexus 6
using oreo rom
cDroid v4 had aptx working for nexus 6
so when i move to another rom it was not working
after flashing this it works again
can someone make magisk version for this
and'' call it aptx enabler for oreo '' for example
If aptx works for you you will see 4 options
If it's not working you will see 3 only
In the Bluetooth settings
Hello everyone, a few weeks ago I dropped my phone and it cracked the rear body of the phone. A few days later I also updated to Android Pie.
I'm not sure, but I think that it has damaged the speaker of the phone (I added the information of the update to Pie because it could also be that it was the update the cause of the problem, but I doubt it), every time I speak on the phone, even at most, I do not feel well the interlocutor.
I tried various solutions and I realized that by modifying a few lines of the file mixer_paths_tavil.xml you can increase at least a bit 'the volume of audio devices on the phone. I identified the lines in question and I copied the file to a PC, then deleted the one on the phone and replaced it with the modified one. Obviously the permissions have been set to 777. As a result, the phone no longer plays any audio. Then I tried, with great effort, various file managers, root explorer, solid explorer, fx, etc.. and I can easily edit the file, but when I save it and restart I still do not hear any sound. If I try to play music I get an error message, like the phone does not support the format, etc..
At this point I tried to do a test: I just added a character in a comment in the same file and I saved: same result, the phone does not make any sound.
From the various guides it seems instead that with any file manager that supports the root it is feasible to modify it but it is not so, so I ask if you have any idea about editing that file.
Thank you!
HarryCustom said:
I tried various solutions and I realized that by modifying a few lines of the file mixer_paths_tavil.xml you can increase at least a bit 'the volume of audio devices on the phone. I identified the lines in question and I copied the file to a PC, then deleted the one on the phone and replaced it with the modified one. Obviously the permissions have been set to 777. As a result, the phone no longer plays any audio. Then I tried, with great effort, various file managers, root explorer, solid explorer, fx, etc.. and I can easily edit the file, but when I save it and restart I still do not hear any sound. If I try to play music I get an error message, like the phone does not support the format, etc
This is basically what some of the various audio mods by @Whiskeyomega do.
How did you identify the files, paths necessary? Pie is different from Oreo and Nougat before that. Did you by chance use Oreo path?
Why not use Refurbish mode in Dev Patched LGUP and go back to pure stock. Bonus points if you go back to Oreo for now until you get your audio straightened out...
You also know the Oreo mixer paths if you want to boost audio more, if you're not sure about the Pie mixer paths.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
ChazzMatt said:
This is basically what some of the various audio mods by @Whiskeyomega do.
How did you identify the files, paths necessary? Pie is different from Oreo and Nougat before that. Did you by chance use Oreo path?
Why not use Refurbish mode in Dev Patched LGUP and go back to pure stock. Bonus points if you go back to Oreo for now until you get your audio straightened out...
You also know the Oreo mixer paths if you want to boost audio more, if you're not sure about the Pie mixer paths.
Click to expand...
Click to collapse
Thank you so much for your reply!
I've simply searched the file mixer_paths_tavil.xml and found it on vendor/etc/ folder.
Sorry but I do not understand what is "Refurbish mode in Dev Patched LGUP".
I am using a stock Pie, TWRP FLASHABLE VERSION (ROM) (v3) (this is the thread: https://forum.xda-developers.com/lg-v30/development/h930-lg-v30-european-market-t3951898).
So do you think that the low volume is due to Android 9 and not to the fall of the phone?
Sure, I can reinstall a stock Oreo and then check if the speaker volume is ok, but I'm getting the feeling that the phone drop is the cause of the problem.
Anyway I can try!
HarryCustom said:
Sorry but I do not understand what is "Refurbish mode in Dev Patched LGUP".
I am using a stock Pie, TWRP FLASHABLE VERSION (ROM) (v3) (this is the thread: https://forum.xda-developers.com/lg-v30/development/h930-lg-v30-european-market-t3951898).
So do you think that the low volume is due to Android 9 and not to the fall of the phone?
Sure, I can reinstall a stock Oreo and then check if the speaker volume is ok, but I'm getting the feeling that the phone drop is the cause of the problem.
Anyway I can try!
Click to expand...
Click to collapse
See post #2 of that thread to downgrade in Refurbish mode back to Oreo, using Dev Patched LGUP. Refurbish mode should completely replace the firmware on the phone.
https://forum.xda-developers.com/showpost.php?p=79964731&postcount=2
See if your audio returns. It should at least reverse any audio editing snafu.
If you still have no audio, then it's something with your hardware.
Sent via open market LG US998 V30/V30+
I replaced the modded mixer_path.xml with the stock xml but it didn't change anything. I thought it is for dual speaker sound.
Flashed Oreo and refleshed Pie but nothing changes, the volume is always very low. Surely the speaker is broken.
Next week I'll try to replace it
Thnk you to everybody!
I have owned LG V30/40/50 primarily for music listening. The downside was to activate the high impedance mode (for earphones under 50 ohm), one had to go through various processes involving adapters and cables. The other option for rooted devices was to edit the MIXER_PATH_TAVIL.XML file. That triggered the high gain output permanently.
For V60, that option is not directly available. The reason is that /vendor/etc/mixer_path.xml is located in super partition making the file not editable. So you could only force the high impedance mode by using adapter or cable option till now.
Using Magisk, I have written two modules that will allow you to substitute the system file and put your phone in high impedance mode permanently. Magisk simply loads the edited files as the effective ones (disabling the system file). You will notice increase in volume/gain when you enable/disable DAC in sound settings.
So I have Viper 4 installed with my module without any problem producing enhanced sound output from V60.
INSTALLATION:
1. Download the attached modules. Do not make any changes.
2. Save it on your phone.
3. Go to Magisk module page and choose install from storage option.
4. If you already have AML installed then uninstall that first.
5. Direct Magisk to the file you just downloaded. Now install AML first.
6. Reboot.
7. Install the Mixer.zip second (for high impedance effect) with Magisk.
8. Reboot.
Enjoy!
This module makes V60 more likable for listening to music. As you said, the new partition structure that is implemented in V60 made it impossible to edit the relevant files un-editable. Of particular value is your AML that does not make any sacrifices when listening in high impedance. Fantastic job!
I was myself thinking of undertaking a similar project but you delivered.
I think that as Android evolves, it is becoming more and more like iOS in terms what you can and can't customize. Thanks to John Wu for creating Magisk! He has extended the customizable life of Android.
I have been looking for a way to force my V60 in high impedance mode to get a boost in volume. There is no solution anywhere on web. I find the solution using an adapter or a cable very inconvenient. Not to mention that using them degrades the audio quality.
You have helped many of us music lovers (who have been looking for a permanent solution) by these modules. They work like charm. I haven’t found any problem so far. V60 sounds better than V50 in high impedance mode with full power of DAC.
As much as I love V60 for many reasons, the lack of triggering high impedance mode was a bummer. Now we are all set to enjoy this excellent phone from every angle.
Thanks man.
THANK YOU so much for this. works beautifully. but how did you get viper4 to work on the v60? i can't seem to figure it out
Actually it is not difficult at all. Since you have already installed the module for high impedance mode, all you need is the Viper 4. I suggest that you install this version of Viper 4. The reason is it is newer.
INSTALLATION:
1. Download the Viper 4.
2. Save it on your phone.
3. Install it as a Magisk module.
4. Reboot.
5. Once rebooted, you activate Viper by turning on the "Master limiter" in the app and configuring your desired options.
P.S.: If you don't want to add any other audio modules (like Dolby ATMOS etc.) then there is no need to install the AML module that is on this page. You can keep it (if desired) but it is not needed.
omg ur a legend! uve given me a 2 eargasms. every single guide says to install the viper4 apk... not the module... thanks again. btw which music player do you use?
Glad to know that you are enjoying the full potential of LG V60 in terms of music! I have the built-in music player that is in V60. The reason is it uses the inherent DAC in the best way. But I also have USB Player Pro.
Most of my music listening is streaming services. And V60 rocks just as much.
Please let us know should you need any help. We are a big and happy family here at XDA.
wondering if you could help me with this issue. i can't seem to get xposed edge and physical buttom master control to work on lsposed. they both install fine with no errors but they just dont work. i also have gravitybox on lsposed which does work so im not sure what the issue is
I don't use the apps that you are referring to. So I am not the right person to guide you in the right direction. However, I hope someone in the forum can help you.
Have you searched the XDA relating to your problem? Maybe it has been discussed earlier somewhere else.
yeah i figured it all out. thanks again
Awesome. Enjoy the best phone for audio listening — V60.
I`m unable to install the AML module. It says: Installation failed! Unsupported / Unknown image format. I also extracted the AML zip file with the same error message when installing. I would be very grateful if you could help me please.
Are you installing it as a Magisk module? I just tested it. It installs and works totally fine.
I`m sorry but I`m a complete noob when it comes to this. This is the very first time I do this. Where should I download Magisk app from. My Magisk app when installed has MODULES section at the bottom completely greyed out, so I cannot select it and under Magisk section up top I`ve got the following:
Installed N/A
Zygisk NO
Ramdisk YES
Under APP section:
Latest 25.2 (25200) (33)
Installed 25.2 (25200)
Package com.topjohnwu.magisk
So it looks like the Magisk app is installed, but not the Magisk itself. Where should I get the Magisk from?
You have to root your V60 that starts with unlocking the bootloader first. The process is well documented in this forum.
Thanks so much! I`ve heard about rooting, but I`ve never done it before. People say, that you might end up with a brick, if rooting process isn`t successful.
No worries.
Royaltiger said:
I have owned LG V30/40/50 primarily for music listening. The downside was to activate the high impedance mode (for earphones under 50 ohm), one had to go through various processes involving adapters and cables. The other option for rooted devices was to edit the MIXER_PATH_TAVIL.XML file. That triggered the high gain output permanently.
For V60, that option is not directly available. The reason is that /vendor/etc/mixer_path.xml is located in super partition making the file not editable. So you could only force the high impedance mode by using adapter or cable option till now.
Using Magisk, I have written two modules that will allow you to substitute the system file and put your phone in high impedance mode permanently. Magisk simply loads the edited files as the effective ones (disabling the system file). You will notice increase in volume/gain when you enable/disable DAC in sound settings.
So I have Viper 4 installed with my module without any problem producing enhanced sound output from V60.
INSTALLATION:
1. Download the attached modules. Do not make any changes.
2. Save it on your phone.
3. Go to Magisk module page and choose install from storage option.
4. If you already have AML installed then uninstall that first.
5. Direct Magisk to the file you just downloaded. Now install AML first.
6. Reboot.
7. Install the Mixer.zip second (for high impedance effect) with Magisk.
8. Reboot.
Enjoy!
P.S.: Audio Modification Library (AML) has been modified to accomodate this module. Now you can use this module with all audio modules in high impedance mode!
Click to expand...
Click to collapse
Will this work on the v50?
If you are fully rooted then V50 allows to fully edit the MIXER_PATH_TAVIL file directly.