{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You flash this MOD at your own risk,
i take no responsibility for any mishaps.
Subscribe to update notifications and general chat by clicking the button below
PIXEL TELEGRAM CHANNEL
This here is my personal setup and thought i'd share. Usually i test extensively before releasing to public, but if you do find something detrimental to the usage of your device that is either Force Closing or simply not working, let me know and i will in turn inform whether that is something i will tend to.
WETA is a rom for Music geeks like me, though because we are still waiting on TWRP to become available i'd thought i'd make this MOD to flash in the meantime. Its main focus is Audio.
This mod installs the following...
V4A 2.5.0.5 or 2.3.4.0
Dolby Atmos
Sony Xperia™ Z5 Premium audio system
Beats™ libraries and effects
WETA Reboot app
How to install...
As of 9.0 moving forward, you will need to flash this mod using TWRP.
NOTE: There have been some issues with systemui crashing after install. This results in having to flash back to stock and in some cases having to wipe phone completely.
I advise running an un-encrypted file system at this stage, which may or may not help. Just be aware that things are basically experimental at these early stages.
1. Make sure you are on Stock firmware and have rooted device
2. Download mod zip
3. Install this app "Root Browser"
4. Extract the zip (click and hold, select extract) using Root Browser directly into Download folder. (you should have /sdcard/Download/WETA_*** as folder with files in it)
5. Go into Download/WETA_*** folder and select WETA-flash.sh
6. Tick "Execute script as root"
7. Then select the Execute button
8. It will say "Executing script"
9. Once complete you should have a popup box with no errrors.
10. Reboot device and mods should be installed....
Changes...
31st Oct
Fixed some things in audio_effects.conf
Added a new mod, 3minit battery to download page
#3 1st Nov
Modified build.props
Added System wide audio
#5 + #5b
Script modifications to be more universal for build.prop mod
- no longer replaces build.prop, now appends to file instead, keeping existing mod lines
V4ADA1 + V4ADA2
V4ADA1 - V4a 2.5.0.5
V4ADA2 - V4a 2.3.4.0
Both these versions have all audio mods omitted as to help with echoing while gaming.
Only V4A and Atmos present.
Fyi.. this can be flashed over the top of previous audio mods
12th NOV
WETA Audio 7 + 7b + V4ADA1_V5 + V4ADA2_V5
removed modification of audio_policy_config file
12th NOV
WETA Audio 8 + 8b + V4ADA1_V6 + V4ADA2_V6
More audio_policy_config tweaks for spotify
WETA Audio 9.0
This version is an Aroma installer version. TWRP only.
WETA Audio 9.1
Fixed V4A convolver and profile permissions
– FYI this will wipe out your /sdcard/ViPER4Android folder
Added Sony music player
Weta reboot option
BusyBox Install option
Weta audio remover
MOD Download Page
If you like my work, please consider buying this poor guy a craft beer for his efforts
?? --->
Downloading now. Will test as soon as I get to work. Thanks!
All the ports are coming left and right for device... we'll see how this one goes
I downloaded the zip and followed the instructions. Already rooted, had busybox and Root browser. Restarted and everything was installed. I keep getting FC on Dolby and when I enabled Viper it didn't change anything. I am not sure what I am missing.
ExcuseTheN00b said:
I downloaded the zip and followed the instructions. Already rooted, had busybox and Root browser. Restarted and everything was installed. I keep getting FC on Dolby and when I enabled Viper it didn't change anything. I am not sure what I am missing.
Click to expand...
Click to collapse
Did you start off with a clean system and vendor? The files going to vendor are important. Also are you using a custom kernel?
Selinux needs to be permissive, if you go into a terminal emulator and type su , allow root, then type getenforce , does it say permissive?
Mentalmuso said:
Did you start off with a clean system and vendor? The files going to vendor are important. Also are you using a custom kernel?
Selinux needs to be permissive, if you go into a terminal emulator and type su , allow root, then type getenforce , does it say permissive?
Click to expand...
Click to collapse
Yes they were clean and it is permissive. I'm on ElementalX 0.05.
---------- Post added at 08:18 PM ---------- Previous post was at 07:20 PM ----------
What is the easiest way to uninstall the mods? I would like to uninstall them and try to reinstall again.
Working great. I do prefer the old Viper though. I think it sounds better. Great job.
wow, I am super excited, I absolutely love your audio Mods coming from the nexus 6p! Thank you very much for bringing your mods forward to the Pixel XL.
2FunJags.
I have tried to get this to work with no success. I did double check and the newest version of busybox is installed. Selinux is set to permissive. I enable the Dolby app and the Viper app but nothing changes. I do not hear any difference with it turn off or on. The Dolby app will crash and FC if I click on play demo and let it sit for a few seconds. I am not sure what is wrong. I do have a custom kernel installed (ElementalX 0.05). I have used this on my Nexus 6p with no issues before but now it just doesn't work on my Pixel. I would like to uninstall it but do not know how to do that. Do I need to perform a full reset to the phone or is there another way to remove the mods and try to reinstall them?
EDIT: Finally got it to work. Came home and reflashed the stock boot.img to go back to stock kernel then reflashed ElementalX 0.05 and re-rooted and reinstalled the mod. Went into Viper and it started to work. Not sure why it wasn't working before but now it works 100%. Thanks again for the mod!
Hey would love to get this working however I seem to be having issues as well, I flashed the elementalx kernel then went through the install process as the instructions listed (using stericsons BusyBox) I note have dolby atmos and viper4android installed but neither are processing, I then read through these posts, checked that selinux was set to permissive (it is) and then cleared my audio_effects.conf that I found in the /etc/ folder and tried reinstalling via the script. Unfortunately still no processing from v4a. If you can think of anything else to check that would be awesome, v4a is the biggest thing I miss coming from my old note 4!
Sent from my Pixel XL using Tapatalk
Thanks for the great mod !
Dolby Works without any issues (except the demo)
Viper didn't work immediately with just on processing:no everything else was on yes , then it worked for a few minutes and went back to no.
I tested with Spotify and Play Music.
[edit]: It seems that it doesn't always know that music is playing and when it starts processing if the music finishes it stops again.
Compatible mode does nothing
exadeci said:
Thanks for the great mod !
Dolby Works without any issues (except the demo)
Viper didn't work immediately with just on processing:no everything else was on yes , then it worked for a few minutes and went back to no.
I tested with Spotify and Play Music.
[edit]: It seems that it doesn't always know that music is playing and when it starts processing if the music finishes it stops again.
Compatible mode does nothing
Click to expand...
Click to collapse
Thanks, ill try something to make the mod systemwide.
--->
I have been testing a lot, as there has been some instances of SystemUI crashing after flashing this, and other mods for that matter. I am adding to the op that at this stage it is advisable to have an unencrypted file system.
To achieve this you need to flash back to stock, (including data) and re root before you boot up into android.
I have also made some mods to the install package to modify vendor/build.prop as well as system/build.prop. This may have been an issue also.
If anyone has any more info on these systemui crashes that would be appreciated.
--->
DELETED
still getting systemui crash
Easiest way to go back to stock?
Sent from my Pixel XL using XDA-Developers mobile app
v2.2v said:
Easiest way to go back to stock?
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
I just pulled link. Just hold off for a bit. I got another systemui crash, but to flash back to stock, fastboot the stock firmware
-->
So i am still getting systemui crashes with these new changes and an un encrypted system... I am going to dumb down the audio mods to just v4a and dolby. and try that for a day,'
hold tight.
--->
So are there any people who have been running the mod successfully since yesterday?
If so i have one question.. have you activated SystemUItuner?
--->
SystemUI Crashes...
So after trying to figure out what he hell is wrong with my mods, ive gone to the SuperSU thread and have read people are having these crash issues, even with an unmodified system. So this is all related to root in general.
Looks like we are going to have to just wait for a fix on the root side of things..... ill be pulling links until there is an update to SuperSU
--->
Shouldn't be long, Chainfire is pretty active in the Pixel root thread and seems to be making some headway.
Related
This is my first legit Android project and XDA thread. Suggestions are encouraged.
These zips simply install Eleven and/or AudioFX and accompanying system files. Keep in mind that Android 5.X does not support EQ switching like KitKat did, so the Android 5.X versions delete MusicFX.apk if it exists. Once all other equalizer apps are gone, AudioFX can take control.
The download folders each contain two different zips. AudioFX-XXXX.zip installs AudioFX only - not Eleven. Eleven+AudioFX-XXXX installs both Eleven and AudioFX. All zips are for the Nexus 4 ONLY.
Changelogs are in the second post.
Installation Instructions:
1. Download to your device
2. Make a nandroid backup if you would like to stay safe
3. Flash zip in your recovery of choice
4. Wipe cache and dalvik cache
5. Profit
Uninstallation Options:
A. Restore your nandroid backup (if you made one)
B. Dirty flash your ROM zip and wipe cache and dalvik cache
ΦDroid said:
I no longer have any interest in continuing support for this. I recently converted to Viper4Android, and let me tell you, it is incredible.
Anyone who is interested in continuing this project is welcome, just let me know and Ill help you get started. It's really quite simple.
I will leave the files on Google Drive for everyone to download (at least for a few months), but will not be updating them again.
Sorry for the bad news.
Click to expand...
Click to collapse
Downloads:
Android 5.X.X
Android 4.4.4
Press that thanks :good: button to let me know they work for you
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Credits:
Cyanogenmod - provides apks, libs, and other system files
XDA Recognized Contributor @xpirt - compiled sdat2img for Windows (extracts .dat files)
Changelogs
Eleven- http://review.cyanogenmod.org/#/q/status:merged+eleven,n,z
AudioFX- http://review.cyanogenmod.org/#/q/status:merged+audiofx,n,z
**I do not modify the system files in these zips at all. All changes are made by CyanogenMod, Google, etc.**
150502:
Updated all files using official cm-12.1-20150502-NIGHTLY-mako build
Mostly bug fixes and UI refinements
150403:
Updated all files using official cm-12-20150403-NIGHTLY-mako build
The changes mostly consist of translations and bug fixes
150227:
Updated all files using official cm-12-20150227-NIGHTLY-mako build
Updated translations
Shake to skip song (Eleven)
New app icons
150130:
Updated all files using official cm-12-20150130-NIGHTLY-mako build
This update mainly includes bugfixes and translations from Cyanogenmod
150110:
Updated all files using official cm-12-20150110-NIGHTLY-mako build
Apollo and DSPManager have been replaced with Eleven and AudioFX, the new defaults in CM12
Renamed thread
141127:
Updated all files with my own cm12 build
Notable change by CM: Material design for DSP Manager :good:
141124:
Initial Android 5.0 support
Updated all files with an unofficial cm12 build released by AndroGeek974 on 11/23/14
Enabled deletion of MusicFX.apk - Android 5.0 only supports one EQ at a time
141031:
Last update with Android 4.4.4 support
Updated all files with cm-11-20141031-NIGHTLY-mako.zip
These zips do not delete MusicFX.apk - KitKat supports EQ switching
Subscribed. Good initiative. Keep updating.
Lot of thanks, @ΦDroid !
Sent from my G2
Vlad Paul said:
Subscribed. Good initiative. Keep updating.
Lot of thanks, @ΦDroid !
Sent from my G2
Click to expand...
Click to collapse
You're welcome. Ill probably stick to a monthly release schedule because it is much harder to make the updates now.
Edit: It looks like I can easily get the updated files if I compile cm12 myself. I'm working on that now and will release an update while I'm at it. It looks like DSP Manager has received a Material design update
Congratulations.
DSP Manager tested and aproved here, Stock 5.0.
Hi.
Root required for this to flash ?
Confirmation: Nexus Experience ROM (5.0) - R6.1 - DSP Manager working flawlessly
pafaisal said:
Hi.
Root required for this to flash ?
Click to expand...
Click to collapse
No, you only need custom recovery.
Worked Fine.....Thanks
Would this possibly work with the Nexus 6?
kevk60 said:
Would this possibly work with the Nexus 6?
Click to expand...
Click to collapse
Probably not considering the hardware is much different but you can give it a try. Just make a backup or something so you can easily fix any problems it causes.
Edit: If my script works right, the zip may not flash at all on a Nexus 6. You may need to remove a line.
ΦDroid said:
Probably not considering the hardware is much different but you can give it a try. Just make a backup or something so you can easily fix any problems it causes.
Edit: If my script works right, the zip may not flash at all on a Nexus 6. You may need to remove a line.
Click to expand...
Click to collapse
I'll give it a try and see. What line possibly needs removed? Thanks.
kevk60 said:
I'll give it a try and see. What line possibly needs removed? Thanks.
Click to expand...
Click to collapse
Before you try anything, just know that your audio could stop working which means you may not be able to make any calls. Know how to repair your system partition beforehand.
You actually may want to try the zips I made for the Nexus 5 instead. They are linked in my signature. There are similar lines in the updater-script in those zips as well that may need to be removed.
Please try flashing your selected zip without modifications first and let me know if it refuses to flash so I know if my script works as designed.
If it will not flash, remove this stuff:
Code:
ui_print("Checking device compatibility");
assert(getprop("ro.product.device") == "mako");
One last thing, I may release zips for the Nexus 6 when CM releases a ROM for it.
DSP material
DSP manager with material design :good:
ΦDroid said:
Before you try anything, just know that your audio could stop working which means you may not be able to make any calls. Know how to repair your system partition beforehand.
You actually may want to try the zips I made for the Nexus 5 instead. They are linked in my signature. There are similar lines in the updater-script in those zips as well that may need to be removed.
Please try flashing your selected zip without modifications first and let me know if it refuses to flash so I know if my script works as designed.
If it will not flash, remove this stuff:
Code:
ui_print("Checking device compatibility");
assert(getprop("ro.product.device") == "mako");
One last thing, I may release zips for the Nexus 6 when CM releases a ROM for it.
Click to expand...
Click to collapse
Thank you for the reply. I appreciate it. Will give it a try.
I flashed the dsp-only-1128.zip. It would not flash. Your script works fine. Removed the two lines of code and it then flashed, however only the eq would work. None of the customizations would work. Music fx was removed. I removed this from the system and flashed DSP_only_n5_tomsvs16.zip and this one flashed fine and everything works. Running this on a nexus 6 running stock lollipop and rooted.
kevk60 said:
I flashed the dsp-only-1128.zip. It would not flash. Your script works fine. Removed the two lines of code and it then flashed, however only the eq would work. None of the customizations would work. Music fx was removed. I removed this from the system and flashed DSP_only_n5_tomsvs16.zip and this one flashed fine and everything works. Running this on a nexus 6 running stock lollipop and rooted.
Click to expand...
Click to collapse
Awesome. I figured the Nexus 5 is a more similar device and would probably be more compatible. I'm considering making a new thread with support for the Nexus 6 soon and I will link it here if I do.
While working on the next update, I found that new CM12 builds do not include Apollo or DSPManager. There is a new music player apk called Eleven. For now updates are on hold. I have attached Eleven.apk if anyone is interested.
AudioFX sounds nothing like DSPManager.
I hope they improve it or bring DSPManager back, at least they way it used to sound, with that awesome punchy bass.
lopardo said:
AudioFX sounds nothing like DSPManager.
I hope they improve it or bring DSPManager back, at least they way it used to sound, with that awesome punchy bass.
Click to expand...
Click to collapse
I really prefer this design so it would be good if they merged this design with the base of DSP Manager
I just got my OP3 and really like it. I'd love it with V4A... but it's not working. The driver doesn't load.
When I try to load SELinuxModeChanger, it errors out saying that it's unable to gain root access (even though SuperSU grants root). Weird.
So is V4A working for anyone?
Sent from my ONEPLUS A3000 using Tapatalk
Yep. I have busy box installed.
Sent from my ONEPLUS A3000 using Tapatalk
Try using A.R.I.S.E on XDA, it is a full package with a lot more than V4A. Furthermore, try to set your linux to permissive.
dont use superuser 2.74
use 2.67
^ I think that I'm trying to use v2.74. I'll find v2.67. Thanks!
-KLH
Confirmed fix. I'm now running v2.67 (Beta) and I'm now able to run V4A. Thanks again, kramer987.
-KLH
Setting it to permissive worked for me, that may help others as I do have v2.74 installed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from SM-G900Pkltespr
Can you turn off auto brightness?
denny1970 said:
Can you turn off auto brightness?
Click to expand...
Click to collapse
If you are referring to me, yes I can.
Sent from SM-G900Pkltespr
THREAD REVIVE! (Happy July 4th to those in US)
I thought that I had V4A working, but it isn't - even though it says that it is. How do I know? Regardless of what you do with the FIREqualizer, the sound remains the same - clearly unchanged. Has anyone run into this?
To recap, this is what I'm running:
* OOS v3.2.0
* SuperSU v2.67 Beta
* Busybox v1.24.2-meefik
* SELinux (set to "permissive")
* V4A v 2.4.0.1
* Google Play Music v6.10.3019C.3013175 (phew)
Here's what I see when I run the driver status check:
Here are other screenshots of V4A that shows the rest of the settings and me changing the FIREqualizer. Throughout, the sound doesn't change.
Now I have heard that OOS v3.1.2+ uses an internal sound driver called DiracHD so 3rd party sound drivers cannot be used. Since XDA members are more knowledgeable, I request either confirmation or a suggested solution.
I am running Divine beats by @TheRoyalSeeker.
Viper and Dolby Included.
Good sound..!
Joyo-rocker said:
I am running Divine beats by @TheRoyalSeeker.
Viper and Dolby Included.
Good sound..!
Click to expand...
Click to collapse
When I flash anything, it doesn't get installed properly. That includes Xposed, Divine Beats. It shows install success in TWRP but it doesn't install.
edios123 said:
When I flash anything, it doesn't get installed properly. That includes Xposed, Divine Beats. It shows install success in TWRP but it doesn't install.
Click to expand...
Click to collapse
That's strange try a another twrp recovery specially Garak's one. And try to dirty flash your ROM again or check permissions in file manager or maybe try mounting system in twrp and flash.
Was your phone bootloooping and has systemless root.
Try these and tell me your progress.
---------- Post added at 01:39 AM ---------- Previous post was at 01:37 AM ----------
kharrigan said:
THREAD REVIVE! (Happy July 4th to those in US)
I thought that I had V4A working, but it isn't - even though it says that it is. How do I know? Regardless of what you do with the FIREqualizer, the sound remains the same - clearly unchanged. Has anyone run into this?
To recap, this is what I'm running:
* OOS v3.2.0
* SuperSU v2.67 Beta
* Busybox v1.24.2-meefik
* SELinux (set to "permissive")
* V4A v 2.4.0.1
* Google Play Music v6.10.3019C.3013175 (phew)
Here's what I see when I run the driver status check:
Here are other screenshots of V4A that shows the rest of the settings and me changing the FIREqualizer. Throughout, the sound doesn't change.
Now I have heard that OOS v3.1.2+ uses an internal sound driver called DiracHD so 3rd party sound drivers cannot be used. Since XDA members are more knowledgeable, I request either confirmation or a suggested solution.
Click to expand...
Click to collapse
That isn't necessarily needed as I am running v4a and Dolby as well.
Same problem here. Cannot install viper drivers, 2.76 supersu, busybox on rails, cannot figure out how to set selinux to permissive.
edios123 said:
When I flash anything, it doesn't get installed properly. That includes Xposed, Divine Beats. It shows install success in TWRP but it doesn't install.
Click to expand...
Click to collapse
This is most likely because you HAVE to mount system in TWRP before you install divinebeats or viper via zip file. It will say it's successful, but nothing gets written to the system partition unless you mount r/w prior first. I cannot say this for xposed, but I do know that the only 'systemless' version worked for me was 85.1 by RomRacer.
Joyo-rocker said:
That's strange try a another twrp recovery specially Garak's one. And try to dirty flash your ROM again or check permissions in file manager or maybe try mounting system in twrp and flash.
Was your phone bootloooping and has systemless root.
Try these and tell me your progress.
---------- Post added at 01:39 AM ---------- Previous post was at 01:37 AM ----------
That isn't necessarily needed as I am running v4a and Dolby as well.
Click to expand...
Click to collapse
Will try that, but it wasn't a problem when I was on 3.1.2.
js042507 said:
This is most likely because you HAVE to mount system in TWRP before you install divinebeats or viper via zip file. It will say it's successful, but nothing gets written to the system partition unless you mount r/w prior first. I cannot say this for xposed, but I do know that the only 'systemless' version worked for me was 85.1 by RomRacer.
Click to expand...
Click to collapse
I've mounted system the very first time too. It doesn't work.
edios123 said:
Will try that, but it wasn't a problem when I was on 3.1.2.
I've mounted system the very first time too. It doesn't work.
Click to expand...
Click to collapse
You just have to mount system in TWRP, than you can flash divinebeats or xtrememusic mod or anything else. Im running v4a on this setup:
OP3 Lite rom 3.2.0
SuperSU - 2.76 (systemless)
Xposed - 85.1 (systemless)
XtremeMusic - 7.5.2
Viper4Android - 2.4.0.1
ARISE
matssa said:
Try using A.R.I.S.E on XDA, it is a full package with a lot more than V4A. Furthermore, try to set your linux to permissive.
Click to expand...
Click to collapse
A little help, will using this module not damage my hardware?
Also, ELI5, how is it better than the default setup on my OP3, I searched ARISE and read what was there, but it turned out o be too technical for me.
Any help is appreciated.
gro0vr said:
A little help, will using this module not damage my hardware?
Also, ELI5, how is it better than the default setup on my OP3, I searched ARISE and read what was there, but it turned out o be too technical for me.
Any help is appreciated.
Click to expand...
Click to collapse
This will not damage your hardware, unless you change the EQ to boost too much the sound of course, like for every mod. Furthermore, ARISE installs some audio libraries issued from Sony, HTC, etc... with Dobly app and Viper4Android. Everything is linked in order to have a good sound audio. Furthermore, some profiles are included in order to load them directly in V4A.
I suggest you download the Exodus 1 with Aroma installation since it's simplified.
kadett-k2 said:
You just have to mount system in TWRP, than you can flash divinebeats or xtrememusic mod or anything else. Im running v4a on this setup:
OP3 Lite rom 3.2.0
SuperSU - 2.76 (systemless)
Xposed - 85.1 (systemless)
XtremeMusic - 7.5.2
Viper4Android - 2.4.0.1
Click to expand...
Click to collapse
See, I told that I've already mounted system.
I'll try once again.
After hundred of unsuccessful attempts of modify the ViPERFX installer to get it working on our stock rom (Marshmallow and Nougat), i found a way.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Available versions:
- ViPERFX 2.5.0.5 version, codename "Beautiful".
- ViPERFX 2.4.0.1 version, codename "Beautiful".
Changelog:
V4A v2.5.0.5 Update
February 12, 2017ViPER4Android (V4A)
ViPER4Android updated to v2.5.0.5
Changes:
0. Emergency fix v2504 – repair load file incompatibility issues.
1. New UI.
2.Add quad-ch convolver support (stereo convolver).
3.Add FET compressor.
4.Support change storage path.
5.Fix bugs.
------------------------------------------
V4A v2.4.0.1 Update
Changes:
1.Fix bugs.
2.New audio effect 'AnalogX'.
3.More optimization.
Pre-requisites:
1) Rooted device.
2) Your device MUST have BusyBox installed (recommended version HERE)
*Flash it from recovery, it's a minimal version.
Installation:
0) Take a backup of your complete System partition with TWRP (just in case).
1) Download and Install "The SELinux Toggler.ver.4.3.9.build.62.apk " (or the available newer at that moment), grant root permissions and disable the enforcement.
2) Download and Install your desired ViPER4Android version (see attachments) from TWRP and then boot to system.
3) Open your ViPERFX app, grant root permissions and install the driver (a dialog should ask you about it), the app may look freezed for 1 or 2 minutes (while doing it), let it work, it's normal.
4) Reboot your device.
5) Open the app and check the driver status, if it says "Normal" then you're done. Just activate V4A-FX from the app and enjoy.
Uninstall:
See post #8
Credits: The ViPER Team - http://vipersaudio.com/blog
Reserved.
Great work, I really had waiting for this a very long time. One question, if I uninstall the SELinux app it affects Viper?
champagne66601 said:
Great work, I really had waiting for this a very long time. One question, if I uninstall the SELinux app it affects Viper?
Click to expand...
Click to collapse
Thanks, yes it needs selinux enf. Deactivated in order to work. But you can also activate the developer mode in the Viper app (settings - dev mode), there is an option (that i didn't test) that change the selinux state. I think this change will persist and you will not have issues whether you delete the selinux toggler app.
Does it works with a custom ROM?
Johann0109 said:
Does it works with a custom ROM?
Click to expand...
Click to collapse
Yes, it works.
is there any way to uninstall it?
Dar Samir said:
is there any way to uninstall it?
Click to expand...
Click to collapse
Yes sure,
How to Uninstall:
- Tap the three lines button (settings) in the ViPER app.
- Select uninstall driver
- Remove the ViPER apk manually, located in "system/priv-app".
- Reboot your device, that's all.
ViPER FX (2.5.0.5) Materilized
I'm glad to share this little file that gives a fresh look to the ViPER4Android App, thanks to @pittvandewitt (the guy who makes the beutiful theme) and to @moonlightdrive (the sir who makes a port to stock 7.0).
It works on any ROM and of course, on stock.
Screenshots:
https://i.imgur.com/JVl1kiq.png
https://i.imgur.com/KQJ7ZzD.png
moonlightdrive said:
After hundred of unsuccessful attempts of modify the ViPERFX installer to get it working on our stock Nougat 7.0 rom, i found a way.
Available versions:
- ViPERFX 2.5.0.5 version, codename "Beautiful".
- ViPERFX 2.4.0.1 version, codename "Beautiful".
Changelog:
V4A v2.5.0.5 Update
February 12, 2017ViPER4Android (V4A)
ViPER4Android updated to v2.5.0.5
Changes:
0. Emergency fix v2504 – repair load file incompatibility issues.
1. New UI.
2.Add quad-ch convolver support (stereo convolver).
3.Add FET compressor.
4.Support change storage path.
5.Fix bugs.
------------------------------------------
V4A v2.4.0.1 Update
Changes:
1.Fix bugs.
2.New audio effect 'AnalogX'.
3.More optimization.
Pre-requisites:
1) Rooted device.
2) Your device MUST have BusyBox installed (recommended version HERE)
*Flash it from recovery, it's a minimal version.
Installation:
0)Take a backup of your complete System partition with TWRP (just in case).
1) Download and Install "The SELinux Toggler.ver.4.3.9.build.62.apk " (or the available newer at that moment), grant root permissions and disable the enforcement.
2) Download and Install your desired ViPER4Android version (see attachments)from TWRP and then boot to system.
3) Open your ViPERFX app, grant root permissions and install the driver (a dialog should ask you about it), the app may look freezed for 1 or 2 minutes (while doing it), let it work, it's normal.
4) Reboot your device.
5) Open the app and check the driver status, if it says "Normal" then you're done. Just activate V4A-FX from the app and enjoy.
Uninstall:
See post #8
Credits: The ViPER Team - http://vipersaudio.com/blog
Click to expand...
Click to collapse
champagne66601 said:
I'm glad to share this little file that gives a fresh look to the ViPER4Android App, thanks to @pittvandewitt (the guy who makes the beutiful theme) and to @moonlightdrive (the sir who makes a port to stock 7.0).
It works on any ROM and of course, on stock.
Screenshots:
https://i.imgur.com/JVl1kiq.png
https://i.imgur.com/KQJ7ZzD.png
Click to expand...
Click to collapse
Both of you: thanks a lot for this development. It works like a charm and installation is as smooth as butter!!
Just need one information: lockscreen visualization and pulse don't work after installing V4A (as musicFX and AudioFX are removed). Is is possible to get V4A with these two customizations or any of them? (Just asking the tweaks if available as like pulse and not intended any development enforcement.)
I'm on AEX ROM. Thanks in advance.
checksamir said:
Both of you: thanks a lot for this development. It works like a charm and installation is as smooth as butter!!
Just need one information: lockscreen visualization and pulse don't work after installing V4A (as musicFX and AudioFX are removed). Is is possible to get V4A with these two customizations or any of them? (Just asking the tweaks if available as like pulse and not intended any development enforcement.)
I'm on AEX ROM. Thanks in advance.
Click to expand...
Click to collapse
Sorry for the delay, wasn't at home.
Well in that case, if you're on AospExtended i pressume that you have Magisk Installed, and if you have it, you can install the ViPER4Android Magisk Module by ahrion.
I used to use this Module when i was using LineageOS (with pulse activated).
v4afx_v1.4.zip
Edit: i forgot to mention that you have to dirty flash your current AEX to get MusicFX/AudioFX again and to remove v4 scripts and files located into system.
moonlightdrive said:
Sorry for the delay, wasn't at home.
Well in that case, if you're on AospExtended i pressume that you have Magisk Installed, and if you have it, you can install the ViPER4Android Magisk Module by ahrion.
I used to use this Module when i was using LineageOS (with pulse activated).
v4afx_v1.4.zip
Edit: i forgot to mention that you have to dirty flash your current AEX to get MusicFX/AudioFX again and to remove v4 scripts and files located into system.
Click to expand...
Click to collapse
Hello Moonlight,
Thank you a ton for your swift response. I have dirty flashed the ROM and then flashed V4Afx module, however the issue remains the same. Probably a clean flashing of ROM would resolve. Will try it later this week and update you the status.
thanks again for the tip.
Rgds,
Samir
I'm on ViperOS LOS 7.1.2 with root and magisk.
Tried to install via Magisk module but nothing happened, phone reboot after install but the apk didn't show up.
---- UPDATE -----
I've installed the ZIP some post above and worked like a charm
thank you very much. After a lot of searching for the viper mod, the only one that worked for me was this one. Xt 1621 Nougat stock 7.0, busybox and SElinux toggler, elementary kernel 1.04. Thanks for a little I go back to M.M.
does it have Dolby >?
tnmsrkr said:
does it have Dolby >?
Click to expand...
Click to collapse
No, it's only original V4a driver.
I Tried 10 Options out on the Internet to try and install Viper on My Moto G4 running Lineage Os 14.1 with Android 7.1.2 version and still cannot install this Darn Viper. Any Help would be Greatly Appreciated....
Touchpad64gb said:
I Tried 10 Options out on the Internet to try and install Viper on My Moto G4 running Lineage Os 14.1 with Android 7.1.2 version and still cannot install this Darn Viper. Any Help would be Greatly Appreciated....
Click to expand...
Click to collapse
Did you follow all the descripted steps in this guide?
It's mandatory to install BusyBox (use the version that i uploaded in the OP) and the SElinux enforcement must be deactivated.
If you're still facing issues, read post #11.
moonlightdrive said:
Did you follow all the descripted steps in this guide?
It's mandatory to install BusyBox (use the version that i uploaded in the OP) and the SElinux enforcement must be deactivated.
If you're still facing issues, read post #11.
Click to expand...
Click to collapse
Yea, I tried all the steps in every Install Option out there. I have been Rooting and Flashing for Years but this has me stumped! I have a full version of the latest BusyBox installed, but I will try the version that OP suggest. As far as the SElinux enforcement...It won't let me deactivate it???
Touchpad64gb said:
Yea, I tried all the steps in every Install Option out there. I have been Rooting and Flashing for Years but this has me stumped! I have a full version of the latest BusyBox installed, but I will try the version that OP suggest. As far as the SElinux enforcement...It won't let me deactivate it???
Click to expand...
Click to collapse
SELinux enforcement must be turned off in order to work, otherwhise the v4a_fx driver will not be properly loaded. The app ("The SELinux toggler") keeps the enforcement disabled (and this should remain in that way, all the time).
I had issues using normal versions of BusyBox, so that's the reason why i recommend that specific flashable version posted in the op.
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
This firmware was developed for the p905. It doesn't apply to the p905v at this time because it's bootloader locked and a custom recovery isn't possible.
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
I'm using nano gapps.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features
https://github.com/crdroidandroid/crdroid_features/blob/9.0/README.mkdn
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Work
All
Known Issues
Rotate buggy a bit
Links:
CrDroid Builds
6. 20191113: november security patch: https://drive.google.com/file/d/1Pfu7y84PAaI4zydNm-Yo9GqcCvK0yOwP/view?usp=sharing
5. 20191023: october security patch: https://drive.google.com/file/d/12-h2_sWcYKQUp_Q0gU7j9NlFMTGmM5Rp/view?usp=sharing
4. 20190812: august security patch: https://drive.google.com/file/d/1yq0q2Va6LkavCKiNBO3yqKP-IRkL8MOh/view?usp=sharing
4. 20190708: july security patch, kernel up to orignal msm8974 lineage kernel, small sensors update: https://drive.google.com/file/d/1sDZ9FplHpiGyyuE19BFtdvYsgNNcF2yE/view?usp=sharing
3. 20190528: may security patch: https://drive.google.com/file/d/1ch9ehxLL8jUylr2X1w55MKUDmikhYAiW/view?usp=sharing
2. 20190219: fix flip, fix mic gain: https://drive.google.com/file/d/1BwhkVYPwzrq8ELHE3q_MhhuCejd2BY4E/view?usp=sharing
1. 20190217: https://drive.google.com/file/d/1w7QjUyuTt4YEdBi4RySbmaZg_g3j26ZH/view?usp=sharing
Gapps
https://opengapps.org
Recovery
Use official 3.0.2-0 version from: https://twrp.me/samsung/samsunggalaxynotepro122qcom.html
or use my twrp version: https://forum.xda-developers.com/galaxy-note-pro-12/development/recovery-twrp-3-1-1-0-t3684802
Sources
Sources: https://github.com/crdroidandroid
Device: https://github.com/Valera1978/android_device_samsung_viennalte
Kernel: https://github.com/Valera1978/android_kernel_samsung_msm8974
Vendor: https://github.com/Valera1978/android_vendor_samsung_viennalte
Thanks
Thanks to CrDroid team
Thanks to LineageOS team
Thank you very much just flashed it on my P905 running good so far!
Is P905 compatible with P900? I'm not familiar with the pertinent diffrences, if any.
I have recognized 3 things :
The notification ton is playing endless in a loop (e. g. happen after install the App (Battery Charge Limit) and connect the Power.... also after reboot :if the charging Level reached... also after reboot: from the trustagebt
The Mic gain is too low for : sound recorder, recorder from WhatsApp, Phone application from WhatsApp, Livechat(Audio) from Postident.
I try the app Microphone Amplifier. Till a little Mic gain was added, the Record in this app was. ok. Without gain, the volume was to low. Uncomfortable there is. no way to save the gain in the System out from this app.
OK Google for example works without any issues
The P905 does not react anymore of the magnet Flip from the cover to switch the screen on/off
dwkindig said:
Is P905 compatible with P900? I'm not familiar with the pertinent diffrences, if any.
Click to expand...
Click to collapse
Unfortunately P900 and P905 has differ hardware (exynos 5420 vs qcom 800). It's not compatible.
mad0701 said:
I have recognized 3 things :
The notification ton is playing endless in a loop (e. g. happen after install the App (Battery Charge Limit) and connect the Power.... also after reboot :if the charging Level reached... also after reboot: from the trustagebt
The Mic gain is too low for : sound recorder, recorder from WhatsApp, Phone application from WhatsApp, Livechat(Audio) from Postident.
I try the app Microphone Amplifier. Till a little Mic gain was added, the Record in this app was. ok. Without gain, the volume was to low. Uncomfortable there is. no way to save the gain in the System out from this app.
OK Google for example works without any issues
The P905 does not react anymore of the magnet Flip from the cover to switch the screen on/off
Click to expand...
Click to collapse
Thanks for feedback.
Flip - I missed that moment, when I added fixes in kernel for p905. Evening will check flip and build
Audio - look like I took a bit more, already discarded audio fixes. Will check today evening.
playing endless in a loop - need to check it in logs, a bit later, may be today\tomorrow.
Valera1978 said:
Thanks for feedback.
Flip - I missed that moment, when I added fixes in kernel for p905. Evening will check flip and build
Audio - look like I took a bit more, already discarded audio fixes. Will check today evening.
playing endless in a loop - need to check it in logs, a bit later, may be today\tomorrow.
Click to expand...
Click to collapse
Hi Valera, it doesn't flash in my device (a p905 that worked well with your previous images). It says:
E3004: This package is for device: viennalte, viennaltexx; this device is .
Updater process ended with ERROR: 7
Error installing zip file ...
I wiped it before, but still it doesn't work.
ultraradical said:
Hi Valera, it doesn't flash in my device (a p905 that worked well with your previous images). It says:
E3004: This package is for device: viennalte, viennaltexx; this device is .
Updater process ended with ERROR: 7
Error installing zip file ...
I wiped it before, but still it doesn't work.
Click to expand...
Click to collapse
This is twrp question (it cannt return name). Look like you have old one.
In any way - right now you can remove check:
extract from crDroidAndroid-9.0-20190217-viennalte-v5.1.zip file: \META-INF\com\google\android\updater-script
remove first 2 lines (assert(getprop("ro.produ......................................)
and add updated updater-script back in archive
Valera1978 said:
This is twrp question (it cannt return name). Look like you have old one.
In any way - right now you can remove check:
extract from crDroidAndroid-9.0-20190217-viennalte-v5.1.zip file: \META-INF\com\google\android\updater-script
remove first 2 lines (assert(getprop("ro.produ......................................)
and add updated updater-script back in archive
Click to expand...
Click to collapse
Thanks. I opted for installing your TWRP and now it does flash and everything works very well (including hotspot), except the microphone which records too low (I suggest you to look for noise cancelation problems).
I believe, I must check, which version I've installed CM or CRDrois... I'm not sure in this moment... Both versions were released at the same time
OK, the first flash from yesterday was CM.
Today I try this Rom:
Simular with sound loop, if I connect the Power for charging (Google is updating all Apps) Only chance to get it silent : push all to 0 (sounds) the tone is parallel to all other sounds.
With this rom I haven't get Magisk Manager to defekt root (Magisk 18.1). It wasn't an issue with CM. With this rom the manager doesn't detect root???
Maybe it's about the app SuperSu from Playstore? Haven't test it right now. I just flash the ROM one again (wipe cache/data/dalvik) Internal SD not. With CM wasn't it possible to mount an USB Stick via OTG cable.
I try to install SuperSU (root & app) afterwards and also to mount an external USB.......
Short update ;
In this rom I can disable the charging notification... (CrDroid settings, near on right hand) the loop is away... that's the good news.
The bad one : I don't receive root access : nor via SuperSu nor via Magisk... Any Hints? A short time I could see teh root settings in the Dev menu, but the corresponding apk did not see root in anycase
mad0701 said:
Short update ;
In this rom I can disable the charging notification... (CrDroid settings, near on right hand) the loop is away... that's the good news.
The bad one : I don't receive root access : nor via SuperSu nor via Magisk... Any Hints? A short time I could see teh root settings in the Dev menu, but the corresponding apk did not see root in anycase
Click to expand...
Click to collapse
Yes, in CrDroid no root options in devs.
But latest Magisk is working great. Install latest Magisk 18.1, then boot and manually install Magisk Manager apk file.
You can do check "safery net" in the magisk manager - it will complete pass.
P.s. mic fixed, flip should fixed too (but I cannt check it right now) - I can make small update for draft check.
Valera1978 said:
Yes, in CrDroid no root options in devs.
P.s. mic fixed, flip should fixed too (but I cannt check it right now) - I can make small update for draft check.
Click to expand...
Click to collapse
I would be interested in an update to check flip cover.
Thanks a lot for continuing the work for that great tablet!
Valera1978 said:
But latest Magisk is working great. Install latest Magisk 18.1, then boot and manually install Magisk Manager apk file.
.....
Click to expand...
Click to collapse
I have used the same Version.... but the Manager 7.0 doesn't detect the Root (18.1) . I have flashed 18.1 some times, reboot ... the Manager didn't saw root. I checked this 3 times ... in between the CM Version ... no luck ?!?!?
Does you install root systemless or let you TWRP patch the System partion ?
Just installed this, Netflix doesn't seem to be working. Can't install it from the play store. (The app is not compatible with this version)
Mad07 said:
I have used the same Version.... but the Manager 7.0 doesn't detect the Root (18.1) . I have flashed 18.1 some times, reboot ... the Manager didn't saw root. I checked this 3 times ... in between the CM Version ... no luck ?!?!?
Does you install root systemless or let you TWRP patch the System partion ?
Click to expand...
Click to collapse
Just checked in the latest 20190219:
1. install crdroid, magisk
2. load into the firmware. install the magisk manager
3. back to recovery and reinstall magisk
4. load firmware
Yesterday, I forgot my eyeglas at work... so only reflash a backup was possible.
In the evening, I give the 19.02 Version a new try.
I'll believe, I know why Magiask Manager didn't see the root: There was also a Bug-Report in the Magisk-Thread, that, if the old Manager is in the Background, the new Manager didn't see Root. On other Hand, I've read, that Magisk dedect root simular as SuperSu. The SuperSu Manager was automaticaly installed from Google Store during Setup the P905 at the first Startup.... I don't should Forget to uninstall SuperSu after first boot
---------- Post added at 12:01 PM ---------- Previous post was at 11:58 AM ----------
Bluewave653 said:
Just installed this, Netflix doesn't seem to be working. Can't install it from the play store. (The app is not compatible with this version)
Click to expand...
Click to collapse
Same as it was in CM 18 (Orego) I've download the apk direct form Netflix ( you can found the link via help on the Netflix HP )
https://netflixhelp.s3.amazonaws.com/netflix-4.16-200217-release.apk
New try with Version 2
Magisk is woerking after uninstall SuperSu
FlipCover Witz Magnet works
Problems:
After each reboot, the Tablett forgot the Standard Launcher (Nova) and New keyboard(Swiftkey)
If the Tablett shoot down with power cable, the shoot down looks like a litte bit irretation
Also it is not possible to Boot the Tablett Düring active charging.
The charging loop sound just be disabled in the settings
Netflix was installed Form the APP store before rooting, hide Magisk, an nupdate was received, working
Thats the first impression after a few Minuten
Usb OTG looks like, that it doesn't work.
There is in this moment no reaction, if I insert an USB with an OTG cable.
Maybe I must change something in the Dev-Settings?
Gesendet von meinem SM-P905 mit Tapatalk
---------- Post added at 06:17 AM ---------- Previous post was at 05:33 AM ----------
The notification Ton has a problem at all, not only with the charging cable. If a notification occurred, the ton is playing in a loop till I pull down the tiles/notification from the top.
I would expect, that this ton is played only one time
1. Install AML and ViperFX
2. Reboot.
3. Launch Viper and install the driver.
4. Without running Viper:
- From the archive AML.rar
replace post-fs-data.sh along the path /data/adb/modules/AML
- From the archive Viper.rar
replace post-fs-data.sh along the path /data/adb/modules/VIPER4AndroidFX
5. Reboot.
6. Done.
Note.
1) My PowerAmp does not work correctly.
2) If there is a clock offset in the status bar then install the module selinux_enforce.zip
Spoiler: Screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[email protected] said:
1. Install AML and ViperFX
2. Reboot.
3. Launch Viper and install the driver.
4. Without running Viper:
- From the archive AML.rar
replace post-fs-data.sh along the path /data/adb/modules/AML
- From the archive Viper.rar
replace post-fs-data.sh along the path /data/adb/modules/VIPER4AndroidFX
5. Reboot.
6. Done.
Note.
1) My PowerAmp does not work correctly.
2) If there is a clock offset in the status bar then install the module selinux_enforce.zip
Spoiler: Screenshot
View attachment 5544989View attachment 5544991
Click to expand...
Click to collapse
Thanks. Can't extract your .rar files, seem corrupted
Bepi Mosto said:
corrupted
Click to expand...
Click to collapse
reload
Finally working in OOS12 thanks!
P.S for some reason the folder directories to copy the files were:
data/adb/modules/aml
and
data/adb/modules/ViPER4AndroidFX
Figured it out when getting directory does not exit when trying the paths given in first post
TY for this. I had it working 100% on Android 11, but figured I was lost on 12. Only issue I've had is it constantly thinks I'm connected to my car radio's BT after I disconnect, so profiles aren't perfect, but I missed V4Android. Sound quality is night vs day.
Hi there,
after several other methods this one helped me to solve the driver problem. Thanks for that!
Still I have the problem that NEON is not activated. Is there any solution to be found anywhere?
I am using the Oneplus Nord 2T with Oxygen OS Android 12.
EDIT: found solution.
This worked fine for me on OOS13, it works in all apps when the legacy mode is on. However after doing this whole procedure, Dolby Atmos no longer works (at least on the integrated speakers, which is what I only tested)
Didn't work. After replacing files Viper driver is installed loop (OnePlus 10 Pro, OOS 13, C20 (EU))
Arcide said:
This worked fine for me on OOS13, it works in all apps when the legacy mode is on. However after doing this whole procedure, Dolby Atmos no longer works (at least on the integrated speakers, which is what I only tested)
Click to expand...
Click to collapse
Did anyone else have this issue and any clue on how to solve it?
Hey guy i installed viper works but when i try to use the Convolver and than i click on impulse response. I get this message on the bottom. Anyway to fix this.
The presets install into a different folder. You have to manually move them over to where Viper is telling you it can't find them. Oddly enough, I had to use Terminal to move them. Even Root Explorer with SU permissions got a r/w denial.
MStrawder said:
The presets install into a different folder. You have to manually move them over to where Viper is telling you it can't find them. Oddly enough, I had to use Terminal to move them. Even Root Explorer with SU permissions got a r/w denial.
Click to expand...
Click to collapse
i Wnet into the folder and i have everytinh there took a screen shot of it.
Am i doing something wrong
I believe its a weird permissions error. There's a guide to getting these to work in the main Viper4Android thread here on XDA.
MStrawder said:
I believe its a weird permissions error. There's a guide to getting these to work in the main Viper4Android thread here on XDA.
Click to expand...
Click to collapse
Would you be able to link to that fix please.
Also i removed viper and verytime it asks me to install drivers and i do and when i reboot start viper it asks me to do it again. Sorry a little frustrated
Viper4Android That's the thread. Its towards the end. As far as troubleshooting, I can only recommend removing all of the modules and starting from scratch. The steps at the top of this thread worked perfectly for me.
MStrawder said:
Viper4Android That's the thread. Its towards the end. As far as troubleshooting, I can only recommend removing all of the modules and starting from scratch. The steps at the top of this thread worked perfectly for me.
Click to expand...
Click to collapse
Someone recommened to install the dolby app and it would work going to try it and let you know.
MStrawder said:
Viper4Android That's the thread. Its towards the end. As far as troubleshooting, I can only recommend removing all of the modules and starting from scratch. The steps at the top of this thread worked perfectly for me.
Click to expand...
Click to collapse
So far nothing i have done has fixed the impulse problem says its not there but the files are in there.
I don't have the link, but Google for Viper4Android 2.7 profiles. A guy has a GitHub page where he's updated them all to work with Viper 2.7. I remember having to download those as the old profiles didn't seem to be recognized.
MStrawder said:
I don't have the link, but Google for Viper4Android 2.7 profiles. A guy has a GitHub page where he's updated them all to work with Viper 2.7. I remember having to download those as the old profiles didn't seem to be recognized.
Click to expand...
Click to collapse
So afterman trys i was able to get the convolver and impulse response to work. One last question on my old one plus 7 pro i have viper installed with a rom on it and i have this layout wanted to know where i could find this version. Also Its the same version i am using but the layout is different.
I can't spot a difference in the two images. It won't enable though until you toggle the Master Power button to on.