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

Which six (choose six) packages best represent the ViPER vision and should remain?


  • Total voters
    375
  • Poll closed .

guitardedhero

Senior Member
Jan 17, 2012
7,941
24,077
0
39
Little Rock
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.
I was asking about the enabled settings in the output tab, like what are all values in Headset tab?

I have Nexus 6 as well since day one and have been using my current profile for quite some time now and do not experience that issue. Do you also experience the issue when using headphones for a voice call?

Take my profile for a spin and see how it performs for the day.
 

darkstar73

Senior Member
May 27, 2013
177
40
58
I was asking about the enabled settings in the output tab, like what are all values in Headset tab?

I have Nexus 6 as well since day one and have been using my current profile for quite some time now and do not experience that issue. Do you also experience the issue when using headphones for a voice call?

Take my profile for a spin and see how it performs for the day.
TBH, I think this mod somehow messes with the microphone settings since I can hear everything fine. It's only the person I'm talking to that has issues.
 

guitardedhero

Senior Member
Jan 17, 2012
7,941
24,077
0
39
Little Rock
TBH, I think this mod somehow messes with the microphone settings since I can hear everything fine. It's only the person I'm talking to that has issues.
You mean ViPER4Android? You claimed this issue with only ViPER4Android installed. If that's the case, it may possibly be a hardware issue. Have you tried all three drivers to see your caller could detect any difference?

Have you experimented with the following /system/build.prop line?

Code:
persist.audio.handset.mic=digital
Add this line at the bottom and test. Then change digital to analog and test again. Reboot after saving any build.prop changes before testing.
 
  • Like
Reactions: deeplyyoung

darkstar73

Senior Member
May 27, 2013
177
40
58
You mean ViPER4Android? You claimed this issue with only ViPER4Android installed. If that's the case, it may possibly be a hardware issue. Have you tried all three drivers to see your caller could detect any difference?

Have you experimented with the following /system/build.prop line?

Code:
persist.audio.handset.mic=digital
Add this line at the bottom and test. Then change digital to analog and test again. Reboot after saving any build.prop changes before testing.
I will try that. Hopefully, it will work because I'm tired of uninstalling viper to have a phone conversation.
 

guitardedhero

Senior Member
Jan 17, 2012
7,941
24,077
0
39
Little Rock
You still testing the lite rom with viper, guitardedhero? Probably held off a bit since you've been busy with the installers
I was testing it here and there on a secondary rom with no root but never could get it to process. I realized last night that testing on MultiROM using primary and secondary I was getting very different results than you guys were so I suspect the case is the same of even worse with a secondary rom with no root. I'll have to find a time to devote to running pure stock with no gimmicks and go from there.
 
G

GuestD0701

Guest
Nexus 6/Pure Nexus rom/Lean kernel here using Dolby atmos light 2.2 and worked great. Flashed over V4A MM once I'd had it installed. Wasn't processing before and now works with Dolby atmos. Tks op!! :)
 

Phrodini

Senior Member
Apr 20, 2012
2,104
750
0
I was testing it here and there on a secondary rom with no root but never could get it to process. I realized last night that testing on MultiROM using primary and secondary I was getting very different results than you guys were so I suspect the case is the same of even worse with a secondary rom with no root. I'll have to find a time to devote to running pure stock with no gimmicks and go from there.
I tried 1.3 on lite rom with cataclysm and it works without any issues. I have a lollipop 5.1.1 as secondary and I'll try to see how 1.3 or even 1.9 work on it. You got your work cut out for you, guitardedhero. You always come through tho.
 
  • Like
Reactions: guitardedhero

guitardedhero

Senior Member
Jan 17, 2012
7,941
24,077
0
39
Little Rock
I tried 1.3 on lite rom with cataclysm and it works without any issues. I have a lollipop 5.1.1 as secondary and I'll try to see how 1.3 or even 1.9 work on it. You got your work cut out for you, guitardedhero. You always come through tho.
Thank you for the kind words, and your helpful and encouraging attitude in helping XDA members does not go unnoticed either.

I honestly feel more progress would've been made if I had not been using MultiROM thi whole time lol. The normal way takes much more time but you'll see what testers see and that is of the utmost importance in a thread like this.

Right now, as a change of pace I've got a rom just zipped up with tons of Xperia™ stuff baked in (no ViPER|Atmos™ stuff) as I want to see what full Sony™ is like, without dseehx of course.

And then, to see **** really get retarded, I'm just about finished with ViPERFX/xHiFi | DD+/Atmos™ - "Now, You're Just Being Stupid"™ Lmt. Ed. with all drivers preinstalled to not further delay the retardation.
 

leondestiny

Senior Member
Jan 12, 2013
2,041
391
0
Seinegald
the trick for me to get it to work was to mount 'system' in twrp recovery ! :)

flashed rom flashed gapps /then mounted system/ then flashed the Viperinstaller and bam ! my audio is enhanced immensively !

i want to ask if any of you guys here have some specific nice profile for BeatsAudio headset? mine are Beats Studio.
i would like nice bass for house music- and old school hip hop.

oh yeah and one more thing, i have installed the one that comes with atmos dolby audio. i have tha app in it too, is there anyone who runs both v4a and dolby audio simultaneously ? i tried but it gets too loud XD so i use v4a only.
 
Last edited:

Tex99

Senior Member
Sep 13, 2012
820
967
0
I love your profile for viper, but with the last Xtreme music update and the new Xtreme music app the audio becames worst in my opinion, not so clean. So I want to try you last work with xhifi. It sounds better than Xtreme music v6 ? Thank you for all your posts,help and work, compliments :)
 

Phrodini

Senior Member
Apr 20, 2012
2,104
750
0
Thank you for the kind words, and your helpful and encouraging attitude in helping XDA members does not go unnoticed either.

I honestly feel more progress would've been made if I had not been using MultiROM thi whole time lol. The normal way takes much more time but you'll see what testers see and that is of the utmost importance in a thread like this.

Right now, as a change of pace I've got a rom just zipped up with tons of Xperia™ stuff baked in (no ViPER|Atmos™ stuff) as I want to see what full Sony™ is like, without dseehx of course.

And then, to see **** really get retarded, I'm just about finished with ViPERFX/xHiFi | DD+/Atmos™ - "Now, You're Just Being Stupid"™ Lmt. Ed. with all drivers preinstalled to not further delay the retardation.
I understand. Some people with how their roms are set up can be different when it comes to installing viper. When I was on a build of pure nexus I had problems getting viper to work but on a stock lite it worked instantly. Yeah with multirom you get to test the build someone is using but like you said it does take time.

I'll probably test out the Sony on 5.1.1 if it works on it since viper/atmos is already working perfectly on 6.0.1
 

Meowdib

Senior Member
Apr 23, 2011
829
347
93
ViPERFx | xHiFi | Atmos™
I tried flashing this over version with Atmos v2.11 but it keeps asking me to install the driver.
Edit: Reflashed ViPERFx | xHiFi | Atmos zip and then the driver afterwards. Now I have the dark viper program and the xhifi program. xhifi asked me to install a driver, I chose the 3rd one. Is this correct?
Edit2: After reboot, xHiFi still asking to install driver. Driver status shows 0.0.0.0. I won't have a chance to reinstall ROM until later tonight.
 
Last edited:
  • Like
Reactions: fedef12evo

guitardedhero

Senior Member
Jan 17, 2012
7,941
24,077
0
39
Little Rock
I tried flashing this over version with Atmos v2.11 but it keeps asking me to install the driver.
Edit: Reflashed ViPERFx | xHiFi | Atmos zip and then the driver afterwards. Now I have the dark viper program and the xhifi program. xhifi asked me to install a driver, I chose the 3rd one. Is this correct?
Edit2: After reboot, xHiFi still asking to install driver. Driver status shows 0.0.0.0. I won't have a chance to reinstall ROM until later tonight.
Definitely want a fresh /system to install on until I have the time to set up the install script to deal with existing files. Cortex with NEON is what you want but be sure to install BusyBox whether you think you have it already or not. XHiFi is definitely more aggressive than FX is and doing this first will satisfy XHiFi once it's installed.
 

Meowdib

Senior Member
Apr 23, 2011
829
347
93
Definitely want a fresh /system to install on until I have the time to set up the install script to deal with existing files. Cortex with NEON is what you want but be sure to install BusyBox whether you think you have it already or not. XHiFi is definitely more aggressive than FX is and doing this first will satisfy XHiFi once it's installed.
Thanks. I restored my clean install and it worked
 
  • Like
Reactions: guitardedhero