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?
Related
Hey guys,
My bluetooth headphones work perfectly on my G Tablet (CyanogenMod 7.1RC REPACK build 21), until I fire up wifi. Whenever there is data transfer on wifi, the audio skips, badly.
Is there any solution for this problem?
Cheers,
Jason
galapogos01 said:
Hey guys,
My bluetooth headphones work perfectly on my G Tablet (CyanogenMod 7.1RC REPACK build 21), until I fire up wifi. Whenever there is data transfer on wifi, the audio skips, badly.
Is there any solution for this problem?
Cheers,
Jason
Click to expand...
Click to collapse
Is the abtfilt program running?
Nope. Can't find that in PS output or on the filesystem.
galapogos01 said:
Nope. Can't find that in PS output or on the filesystem.
Click to expand...
Click to collapse
Alright, then. Install the attached zip file using CWM and see if adding the abtfilt program (from my GtabComb-b3.3-bl11) fixes the BT audio drop issue. This is what's done in CyanogenMod to fix the problem on Android phones.
Tried it tonight. Completely broke audio, lots of errors in logcat. Killing the daemon didn't stop the errors when attempting to play nor fix the audio.
I reflashed the nightly 21 build as I use this thing daily. Without about bt audio, though
Jason
galapogos01 said:
Tried it tonight. Completely broke audio, lots of errors in logcat. Killing the daemon didn't stop the errors when attempting to play nor fix the audio.
Click to expand...
Click to collapse
So much for that quick fix, then. Get me a dmesg and logcat output (see this post for the commands to use).
And, for the next time, you can simply a) either delete /system/bin/abtfilt or b) rename it and then reboot the system--there is no need to reflash the ROM.
Not so sure about that. I'm using the 'CM7 build 21 repack' with 1.2bl. I think the .zip did funny things to /boot.
Do you want the logs with or without abtfilt?
galapogos01 said:
Not so sure about that. I'm using the 'CM7 build 21 repack' with 1.2bl.
Click to expand...
Click to collapse
Apologies. I don't have bluetooth headphones, so this script I didn't test before sending it out. I got the order of the tests wrong (along with a couple of other inconsequential bugs) in one of the scripts so the command to start the abtfilt program was never added to /init.rc.
Try the new attachment in my post.
I think the .zip did funny things to /boot.
Click to expand...
Click to collapse
Define funny here. I doubt my script will screw up your /boot, but, feel free to send me your /init*.rc files if you feel otherwise.
Do you want the logs with or without abtfilt?
Click to expand...
Click to collapse
Both, preferably.
abtfilt was definitely running with the original file from the first post.
When I can handle reflashing this thing again I will give it a shot. Last time I lost 2 hours to it! I should have tested the stock TnT rom.
galapogos01 said:
abtfilt was definitely running with the original file from the first post.
Click to expand...
Click to collapse
Yeah, the abtfilt program is not present in the ROM zip file, but, is still started in /init.nvidia.rc.
I'd like to start by saying, I am a new member so, I was not able to simply ask in that thread and this is the most relevant place to ask. Here is the link to that thread, http://forum.xda-developers.com/showthread.php?t=2293133 . Now, I am on the ME7, so, no TWRP or CWM and I searched all through that file in root explorer and couldn't find any of text required to change, the audio hack is confirmed working for I545. I already searched that thread, no luck. Now that you know my situation, is it possible to download those flash-able files, and either flash them in stock recovery, or take each individual file and place them in the correct directory using root explorer, fix the permission and it work? I'd prefer not to take risks with this locked bootloader, a simple problem with this phone turns it into a paper weight.
Banana Republic said:
I'd like to start by saying, I am a new member so, I was not able to simply ask in that thread and this is the most relevant place to ask. Here is the link to that thread, http://forum.xda-developers.com/showthread.php?t=2293133 . Now, I am on the ME7, so, no TWRP or CWM and I searched all through that file in root explorer and couldn't find any of text required to change, the audio hack is confirmed working for I545. I already searched that thread, no luck. Now that you know my situation, is it possible to download those flash-able files, and either flash them in stock recovery, or take each individual file and place them in the correct directory using root explorer, fix the permission and it work? I'd prefer not to take risks with this locked bootloader, a simple problem with this phone turns it into a paper weight.
Click to expand...
Click to collapse
You cant flash in stock recovery but you should be able to extract the files and then copy/paste them. Make sure they have the right permissions and you should be go to. I would add .bak extension to the stock ones just in case you dont like the mod and want to revert back to stock.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
If you want a great sound app get Viper4Android.
Tool Belt said:
If you want a great sound app get Viper4Android.
Click to expand...
Click to collapse
Did a search on the market for this and the only one I can come up with is all in chinese.
Look here, you will find links in the second post, but read one, two and three.
http://forum.xda-developers.com/showthread.php?t=2191223
Tool Belt said:
Look here, you will find links in the second post, but read one, two and three.
http://forum.xda-developers.com/showthread.php?t=2191223
Click to expand...
Click to collapse
Tried to install everything and to say the least it was unsuccessful I couldn't get the drivers working I tried A8 Neon and A9/A15 Neon neither worked
All I can tell you is it works fine for me and ROCKS PowerAmp
Tool Belt said:
All I can tell you is it works fine for me and ROCKS PowerAmp
Click to expand...
Click to collapse
What drivers did you use and did you put the apks in system/apps or did you install it normally?
Banana Republic said:
Tried to install everything and to say the least it was unsuccessful I couldn't get the drivers working I tried A8 Neon and A9/A15 Neon neither worked
Click to expand...
Click to collapse
Lol, You got one step further than me. Seems I'm too stupid to follow that thread so I didn't even attempt.
Banana Republic said:
What drivers did you use and did you put the apks in system/apps or did you install it normally?
Click to expand...
Click to collapse
I placed it in /system/app
Sorry, I don't recall what driver. I think it suggested on when I installed it. There is a ton of information as to FAQ's and troubleshooting in that thread.
I am also in the same boat...
In call volume on S4 ME7 sucks. Was looking for volume booster specific to S4 ME7.
Found 2 threads:
1. Volume booster mod: http://forum.xda-developers.com/showthread.php?t=2298946
2. Viper4Android http://forum.xda-developers.com/showthread.php?t=2191223&page=640
Tried to read through both treads...
Have couple Q, still unclear for me regarding above:
1. Applying 1st mod - does it distort the sound quality?
2. Does Viper actually allow to INCREASE VOLUME besides improving quality of decoding lossy music files?
PS. Does it make sense to even try those volume improving apps from market? (Volume +, Music volume EQ, ect?)
Thanks!
Don't know if V4a will increase call volume, but it will boost the hell out of your earphone volume on music apps. BUT as the boost increases, so does the noise.
lazer9 said:
Lol, You got one step further than me. Seems I'm too stupid to follow that thread so I didn't even attempt.
Click to expand...
Click to collapse
Some guy on that thread rewrote the installation guide(apparently the guy is Chinese explains EVERYTHING) his guide required wiping dalvik and this good ol' ME7 just won't tolerate any kind of customization
Banana Republic said:
Some guy on that thread rewrote the installation guide(apparently the guy is Chinese explains EVERYTHING) his guide required wiping dalvik and this good ol' ME7 just won't tolerate any kind of customization
Click to expand...
Click to collapse
And yet, following the instructions on the thread I linked to it works very well on my ME7. I wish I could I could do more to help you.
Sorry.
Have you tried this post http://forum.xda-developers.com/showpost.php?p=42944438&postcount=22 in this thread http://forum.xda-developers.com/showthread.php?t=2335869&page=2 ?
Tool Belt said:
And yet, following the instructions on the thread I linked to it works very well on my ME7. I wish I could I could do more to help you.
Sorry.
Have you tried this post http://forum.xda-developers.com/showpost.php?p=42944438&postcount=22 in this thread http://forum.xda-developers.com/showthread.php?t=2335869&page=2 ?
Click to expand...
Click to collapse
I want to make sure I'm doing everything correct this is what I did
1. Download latest zip files
2. copy apks to /system/apps
3. reboot just because I wanted to
4. start apps grant root and download A8 neon drivers and Ax Neon
5. reboot once more
6. Check driver status, enabled: no
7. settings>sound>ViperFx
8. Repeat 1-7 with no justification
Am I skipping a step here, getting the wrong drivers, or what?
I am just using the XHIFI with (I think) xA8 with neon. I copied it to /system/app, I did boot to recovery and wiped cache, but the little android dude looked dead and I am not sure it worked. With root explorer I changed the permission to owner read, write execute, then opened the app, update the driver, enabled it under sound.
I did this a bit ago, and I think this is what I did. But given the difficulty people are having I am not interested in uninstalling and trying to document how I re-install. Keep at it, it does make a big difference.
Tool Belt said:
I am just using the XHIFI with (I think) xA8 with neon. I copied it to /system/app, I did boot to recovery and wiped cache, but the little android dude looked dead and I am not sure it worked. With root explorer I changed the permission to owner read, write execute, then opened the app, update the driver, enabled it under sound.
I did this a bit ago, and I think this is what I did. But given the difficulty people are having I am not interested in uninstalling and trying to document how I re-install. Keep at it, it does make a big difference.
Click to expand...
Click to collapse
The universe aligned just right to allow it to FINALLY work thank you for all your help the ultimate solution was to go into build.prop and edit the 3 lines he suggested I assumed samdung wouldn't do this I will no longer assume anything else for samdung
Banana Republic said:
The universe aligned just right to allow it to FINALLY work thank you for all your help the ultimate solution was to go into build.prop and edit the 3 lines he suggested I assumed samdung wouldn't do this I will no longer assume anything else for samdung
Click to expand...
Click to collapse
EXCELLENT. Play with it for a while and tell me (us!) what you think!!!
Tool Belt said:
EXCELLENT. Play with it for a while and tell me (us!) what you think!!!
Click to expand...
Click to collapse
I would have liked a little bit more of a boost in volume but the quality boost overall is tremendous Compatibility mode is broken they work well separately I'd say so far that it was well worth the trouble I went through
You can keep boosting volume with Playback Gain Control..... but noise will raise its angry head
Sent from my SCH-I545 using XDA Premium 4 mobile app
Over at the Chromecast forum they're building a compatibility list for mirroring with Chromecast. DNA isn't officially supported (yet), but I aim to build a list of ROMS that mirror successfully with the MirrorEnabler app.
TESTED WORKING:
Google Play Edition
Nusense Six
Cyanogen (all music players force close
LiquidSmooth (audio only)
NOT WORKING:
AOKP
Carbon
Paranoid
Dirty Unicorns
Viper
Anyone willing to report on tested and working ROM's please chime in....
Credit goes to r3pwn for his original thread HERE (
r3pwn and I got things rolling on cm-11 so that is confirmed. In the case of DNA ROMs any aosp and cm based should work without issue with v3. It seems the only folks having problems right now is because their ROMs did not compile in r_submix support.
Sent from my HTC6435LVW using XDA Free mobile app
mattgyver83 said:
r3pwn and I got things rolling on cm-11 so that is confirmed. In the case of DNA ROMs any aosp and cm based should work without issue with v3. It seems the only folks having problems right now is because their ROMs did not compile in r_submix support.
Sent from my HTC6435LVW using XDA Free mobile app
Click to expand...
Click to collapse
I noticed the headway made over there with v3 and v4. v4 seems to cast without gps fc but only a black screen. Going to try v3 if i can find it now that the app has been updated.
xlxcrossing said:
I noticed the headway made over there with v3 and v4. v4 seems to cast without gps fc but only a black screen. Going to try v3 if i can find it now that the app has been updated.
Click to expand...
Click to collapse
Here is how mine got working, mind you post these instructions I never had to flash past v2. If you already flashed v3 or greater then you probably don't need to do steps 1 and 2 because Mirror enabler handles that part.
Install and enable mirror enabler v2
execute the following commands in a root terminal
Code:
su
/data/data/com.r3pwn.mirrorenabler/lib/libhackyworkaround.so /data/data/com.google.android.gsf/databases/gservices.db
insert into overrides (name, value) values ('gms:cast:media:use_tdls', 'true');
.exit
exit
Code:
su
/data/data/com.r3pwn.mirrorenabler/lib/libhackyworkaround.so /data/data/com.google.android.gsf/databases/gservices.db
insert into overrides (name, value) values ('gms:cast:remote_display_enabled ', 'true');
.exit
exit
Update /etc/audio_policy.conf and in the global_configuration append to the end of the "attached_input_devices" line
Code:
|AUDIO_DEVICE_IN_REMOTE_SUBMIX
Now, this is something to ask r3pwn but I believe hes pushing a rather generic version of audio_policy.conf and not the device specific policy which means there could be an error related to the generic version. I am not sure if Mirror Enabler is backing up the original audio_policy.conf and putting it back in place after its "disabled" and then uninstalled. What I suggest if you are post v3 is to extract the specific audio_policy.conf from the original ROM and follow step 3 only then reboot. That may be worth attempting to see if it fix.
OK so extracted default audiopolicy, added the submix edit and pushed to system/etc. I am able to receive sound while casting but TV screen is black.
xlxcrossing said:
OK so extracted default audiopolicy, added the submix edit and pushed to system/etc. I am able to receive sound while casting but TV screen is black.
Click to expand...
Click to collapse
Two questions;
What rom are you using?
Did you place the file in /etc/ or /system/etc ? It goes in /etc/
Also make sure the file is owned by root and has 644 perms
I can confirm, NusenseSIX RC 6.4 works as well.
mattgyver83 said:
Two questions;
What rom are you using?
Did you place the file in /etc/ or /system/etc ? It goes in /etc/
Also make sure the file is owned by root and has 644 perms
Click to expand...
Click to collapse
Liquid Smooth. The paths are the same. The permissions are set as they should be. My issue with liquid is no video so tinkering with the audio policy file doesn't seem like a remedy. Ive rebooted Chromecast and the phone to no avail. Can anyone else confirm only audio on LiquidSmooth?
xlxcrossing said:
Liquid Smooth. The paths are the same. The permissions are set as they should be. My issue with liquid is no video so tinkering with the audio policy file doesn't seem like a remedy. Ive rebooted Chromecast and the phone to no avail. Can anyone else confirm only audio on LiquidSmooth?
Click to expand...
Click to collapse
Sorry, I cant directly confirm this for Liquid Smooth but like I said if it can be confirmed by the ROM developer that REMOTE SUBMIX support is compiled into the ROM then using mirror enabler _should_ work. I would suggest contacting the developer to see if this is the case. I can confirm that on my DNA using CM11 m8 snapshot all audio and video works flawless across all applications (including apollo, etc). I would suggest for anyone having issues running that ROM (or possibly others) to attempt the steps I noted earlier to see if using a more "pure" audio_policy.conf. Based on what we learned by testing with my device somehow the audio_policy.conf does in fact have something to do (were not entirely sure what) with ensuring that all the data gets across to the chromecast, he saw a few logcats of users who had audio and no video which were corrected after implementing the "force close fix" that pushes the updated audio_policy.conf. Now while a one size fits all audio_policy.conf is the best method and not causing other issues is hard to say.
Sorry I couldn't be of more help, Good luck!
Edit: I did a few more tests when i got home to make sure I'm not completely full of it and it turns out yeah i am. Apollo is in fact not working for me and does cause a fc then causing mirroring FC's but it appears the force closes settled down after a reboot also plex decided to give me a fit while also while mirroring but otherwise i didn't get any other grief.
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.
STANDARD DISCLAIMER: I am not responsible for any damages caused to your phone. I am not responsible for any hearing loss, please listen at a safe volume level. Use this mod at your own risk there is no warranty or guarantee.
This mod will enable your Quad DAC & enable LGMusic player.
If not rooted with Oreo on H910 link
build.prop mod + Force true 24 bit 44.1 kHz link
Version 1.1
Updated twrp install script
Just flash on top of older versions
Version 1.2
Updated group file permissions, this should not cause an issue with v1.1 but I wanted to correct it. Just flash on top of older versions
Version 1.3
Fixed a permission error. Just flash on top of older version to update.
Should work on other lgv20 phones that never had LG Music Player installed from the factory.
Note: This mod will only work on Stock Oreo 8.0 rooted, wont work on LineageOS
.
Requirements:
Root /w twrp
Stock Oreo 8.0
Never had with LGMusic player installed from the factory.
No LGMusic player apk installed on your phone.
You can Flash the mod in twrp or follow the guide.
Guide Enable DAC & LGMusic player.
First download the H918 rom H91820f.zip You can download it from mega, should download fast.
[Rom][Oreo][Rooted] T-Mobile H918 [20f] [20g] [20h] Oreo flashable
Then extract the zip file.
mount system.img on your computer.
Then copy the five folders and one file from the mounted image, to your phone in the same directory structure listed below. Overwrite.
/system/priv-app/LGMusic
/system/priv-app/LGMusicWidget
/system/priv-app/LGMusicController
/system/etc/com.lge.music.xml
/system/vendor/overlay/com.lge.music
/system/vendor/overlay/com.lge.sizechangable.musicwidget.widget
You should not have to change the file permissions if using a root file manager. in Android. But if you using adb or twrp file manager you may have to.
File permissions to 0644
/system/etc/com.lge.music.xml
/system/priv-app/LGMusic/LGMusic.apk
/system/priv-app/LGMusicWidget/LGMusicController.apk
/system/priv-app/LGMusicController/LGMusicWidget.apk
/system/vendor/overlay/com.lge.music/com.lge.music.apk
/system/vendor/overlay/com.lge.sizechangable.musicwidget.widget/com.lge.sizechangable.musicwidget.widget.apk
Restart phone.
Credits, A Special Thank You
@dudeawsome for providing the H918 rom XDA
I'm guessing this has no effect on Bluetooth audio quality? Only when using a wire?
thejjmax said:
I'm guessing this has no effect on Bluetooth audio quality? Only when using a wire?
Click to expand...
Click to collapse
That's a good question and I am glad you asked it. Because I forgot include that answer in my guide. So to answer you question, there is a noticeable difference in sound quality with using Bluetooth. I am using aptx hd, as for sbc Bluetooth I am not sure. But you are correct a wired headset should get up-scaling to 32 bit sound with LGMusic player.
thejjmax said:
I'm guessing this has no effect on Bluetooth audio quality? Only when using a wire?
Click to expand...
Click to collapse
Oh I forgot to mention that the sound on the internal speaker has improved also. I am using the build prop tweaks that enables system wide Quad DAC support in any app.
Unlock the FULL Potential of the Lgv20's Quad DAC. (root only)
There is a twrp file you can flash now to enable the dac support.
Many thanks for this. Flashed the TWRP zip and it worked flawlessly. Now have working LG Music on my H910 for the 1st time ever. Yes, it's still my daily driver...
q1nt said:
Many thanks for this. Flashed the TWRP zip and it worked flawlessly. Now have working LG Music on my H910 for the 1st time ever. Yes, it's still my daily driver...
Click to expand...
Click to collapse
Your welcome, glad you enjoy it.
This TWRP zip doesn't do the build.prop mod to Force true 24 bit 44.1 kHz does it?
The build.prop mod + Force true 24 bit 44.1 kHz .zip linked in the first post enables it. Haven't tested 24/44, but ADB test with the mod installed showed 16/44 does not get interpolated to 16/48 and 24/192 plays natively. So I doubt there would be any problem with 24/44