* ViPER|Audio || ViPER|Atmos || ViPER|DD+ 4.8/5.5 * Driver * Stock * Sony * Beats *

[guitardedhero]

Same issue with 2.1.3. Thx OP for your efforts and time.

yes, nothing installs...

Nothing installs at all? What device and rom?

I flashed 6.0.1 as a new secondary rom and booted up and restored apps. I rebooted to recovery and flashed ViPER|Atmos 2.1.3 Dark and everything was flashed. I set up v4a and got it processing after disabling and enabling speaker tab. I then opened Dolby Atmos and changed eq to open to get it processing. I then booted to recovery and flashed ViPER|Atmos 2.1.4 Dark which only removes the mount /data lines from 2.1.3, and I may have wiped Dalvik and Cache afterwards before rebooting. Everything was still intact like nothing had changed.

I'm going to test my son's Nexus 5 and 2013 7 now.

 

[Dushy007]

I'm getting' IR sample directory is empty'
Created kernel folder but no luck

Sent from my A0001 using Tapatalk

 

[Akoolive]

Nexus 5
Latest cataclysm
Latest Elementalx

 

[guitardedhero]

Reverted back to 2.0 for now. All the same stuff, the only changes since 2.0 have been script and flashing changes. Confirmed no apk's on my son's Nexus 5. Thanks for all the feedback guys, from now on I'm going to go by one of my favorite sayings:

"Don't be helpful, be harmless"

 

[Akoolive]

Reverted back to 2.0 for now. All the same stuff, the only changes since 2.0 have been script and flashing changes. Confirmed no apk's on my son's Nexus 5. Thanks for all the feedback guys, from now on I'm going to go by one of my favorite sayings:

"Don't be helpful, be harmless"

Thanks for your time and work. Definitely appreciate it.

 

[guitardedhero]

Absolutely, thank you for hanging in there. I wiped System in TWRP and flashed stock 6.0.1 Deodexed on the Nexus 5, booted up to make sure it was clean and had enough free /system space, and flashed ViPER|Atmos 2.0 Light and everything is running great.

I'm not discouraged as I learn the most from mistakes and failure, but I am truly disappointed in my incorrect, possibly unreasonable, assumption that MultiROM is a true representation of what you guys are starting with. It's crazy how everything seemed to always work for me when others had issues, even on my primary rom I would have the same success. I feel it is only fair to you guys that I rid MultiROM from my device to be able to properly test stuff before saying it's ready and wasting so much of your valuable time; as for myself, knowledge and experience is gained so I don't feel it to be wasted time for me but that's obviously, nor should it be, the case for you guys.

To be clear, this is certainly not a rant or a lynching of MultiROM as it is a fantastic tool to do all sorts of things but I believed it to be something it is not (my own fault/problem) and it has prohibited me from accomplishing what I'm trying to do in creating what I hope will one day be the "standard" and "go-to" ViPER Installer.

Thanks again for all the feedback and hanging in there with me.

 

[NOSTALGIA]

just got crackling again. and now its very prominent.. cata, hells, franco... seems. anyone else with other kernels??

 

[Mar-cel]

Nothing installs at all? What device and rom?

I flashed 6.0.1 as a new secondary rom and booted up and restored apps. I rebooted to recovery and flashed ViPER|Atmos 2.1.3 Dark and everything was flashed. I set up v4a and got it processing after disabling and enabling speaker tab. I then opened Dolby Atmos and changed eq to open to get it processing. I then booted to recovery and flashed ViPER|Atmos 2.1.4 Dark which only removes the mount /data lines from 2.1.3, and I may have wiped Dalvik and Cache afterwards before rebooting. Everything was still intact like nothing had changed.

I'm going to test my son's Nexus 5 and 2013 7 now.

Device: klte
Roms tested: CM13 and CM12.1

 

[guitardedhero]

2.2 is a finalized version of the installation process I had in mind working on 2.0 base before I got sidetracked with an alternate update-binary method. Testing is now realistic on my end with the termination of testing on MultiROM recovery. It is no longer on my Nexus 6. I put together an uninstaller to fulfill a user's request so I figured I would share it here for a bit. Neus 6 only as it is flashing the stock files edited by ViPER|Atmos™ and ViPER|Audio™ from the MMB29K Nexus 6 image. The only edit the uninstaller does not touch is the ViPER4Android™ entries in /system/build.prop since I have not looked into it yet and would need plenty of time for testing before I do anything to subtract from your build.prop. This manual last step is very easy or the novice tinkerer and is only necessary on versions 2.0 and below as I have removed the /system/build.prop entries as I have deemed them unnecessary and likely problematic starting with version 2.2.

 

[Mar-cel]

2.2 is a finalized version of the installation process I had in mind working on 2.0 base before I got sidetracked with an alternate update-binary method. Testing is now realistic on my end with the termination of testing on MultiROM recovery. It is no longer on my Nexus 6. I put together an uninstaller to fulfill a user's request so I figured I would share it here for a bit. Neus 6 only as it is flashing the stock files edited by ViPER|Atmos™ and ViPER|Audio™ from the MMB29K Nexus 6 image. The only edit the uninstaller does not touch is the ViPER4Android™ entries in /system/build.prop since I have not looked into it yet and would need plenty of time for testing before I do anything to subtract from your build.prop. This manual last step is very easy or the novice tinkerer and is only necessary on versions 2.0 and below as I have removed the /system/build.prop entries as I have deemed them unnecessary and likely problematic starting with version 2.2.

thanks, this version 2.2 works now great for me

Sent from my SM-G900F using XDA Premium 4 mobile app

 

[nixie2121]

hello. right now I have an older version of viper working fine with a permissive kernel on 6.0.1. what do I need to do to make it work with an enforcing kernel? thanks so much.

 

[guitardedhero]

hello. right now I have an older version of viper working fine with a permissive kernel on 6.0.1. what do I need to do to make it work with an enforcing kernel? thanks so much.

Flashing 2.2 of your choice should be enough.

 

[mseliga]

just got crackling again. and now its very prominent.. cata, hells, franco... seems. anyone else with other kernels??

I flipped over to this from another Viper mod and having the same thing. Messing around with a few kernels, getting it a lot. Seems with Dolby turned off I'm not getting it. For reference I had the Dolby settings as guitar suggested in the OP. rey, do you have Dolby installed and enabled?

 

[nixie2121]

Flashing 2.2 of your choice should be enough.

thank you very much!

 

[bladebuddy]

I flipped over to this from another Viper mod and having the same thing. Messing around with a few kernels, getting it a lot. Seems with Dolby turned off I'm not getting it. For reference I had the Dolby settings as guitar suggested in the OP. rey, do you have Dolby installed and enabled?

Definitely connected to the kernels you are using, had the same problem mainly on kernels that use faux sound e.t.c. better sometimes to stick to a stock kernel.

 

[darkstar73]

I have an issue with the mod and calls. When I'm on a call, if I have this mod installed, the other person always says there is noise on the line or they can't hear me well. It is more pronounced if I'm on speaker. This happens no matter if I'm on stock, a custom ROM, or a custom kernel. There only way I can get it to go away is to uninstall Viper. Un-enabling Viper doesn't help. Anybody else have this issue or know how to fix it? Also, the uninstaller zip in the OP doesn't work.

 

[guitardedhero]

I have an issue with the mod and calls. When I'm on a call, if I have this mod installed, the other person always says there is noise on the line or they can't hear me well. It is more pronounced if I'm on speaker. This happens no matter if I'm on stock, a custom ROM, or a custom kernel. There only way I can get it to go away is to uninstall Viper. Un-enabling Viper doesn't help. Anybody else have this issue or know how to fix it? Also, the uninstaller zip in the OP doesn't work.

Pretty sure Dolby Atmos is the culprit here, especially if set to Open Intelligent EQ. Try setting the EQ to Flat/Manual and turn off all three effects on the bottom. Test a voice call with these adjustments and I bet it will improve quite a bit.

 

[darkstar73]

Pretty sure Dolby Atmos is the culprit here, especially if set to Open Intelligent EQ. Try setting the EQ to Flat/Manual and turn off all three effects on the bottom. Test a voice call with these adjustments and I bet it will improve quite a bit.

I turn Dolby Atmos off when I'm not using it. Plus, I've has this issue with Viper long before you paired it with Atmos.

 

[guitardedhero]

I turn Dolby Atmos off when I'm not using it. Plus, I've has this issue with Viper long before you paired it with Atmos.

On more than one device?

What all is enabled in v4a?

If through speaker then uncheck Sound Optimization and I am also assuming that Lock Effect Mode is inactive.

 

[darkstar73]

Pretty sure Dolby Atmos is the culprit here, especially if set to Open Intelligent EQ. Try setting the EQ to Flat/Manual and turn off all three effects on the bottom. Test a voice call with these adjustments and I bet it will improve quite a bit.

If through speaker then uncheck Sound Optimization and I am also assuming that Lock Effect Mode is inactive.

On more than one device? I only have a Nexus 6.
What all is enabled in v4a? I only have Headset enabled, but I un-enable it when not listening to music. I have never enabled Speaker as I always use headphones when listening to music.