Database Users

ALSA on the Nexus 4 (temporary volume control)

Please remember to make a backup image of your phone before experimenting.
============ WARNING!! =============
The highest setting is VERY loud (as I found out) and could potentially rip apart the speaker on your phone!
Exercise extreme caution when using this. You risk permanent damage to your phone and your ears.​
2013-Jan-20
-----------------
Thanks xda-developers members "skvalex" who wrote ALSAMixer and "chdlock" who is helping me figure out
how ALSA is mapping the audio chipset, we can now temporarily adjust the Digital Volume on the Nexus 4.
Unfortunately, the selected volume doesn't "stick" because the audio driver re-writes it every time it re-opens an audio stream.
A stream is usually opened when a music track begins to play so then the digital volume will reset back to default.
We need a kernel developer to modify the audio driver so it opens an audio stream using a user-selected Volume level.
***
If you don't mind setting the volume frequently or just want to try this out here's what you need:
1) Get ALSAMixer from the Play Store. It was updated recently and you need the latest version.
Please consider a donation to the author.
2) You can re-program the audio chipset by editing fields in ALSAMixer. Here is a list of what we can control so far.
Headphones volume:
Left: RX1 Digital Volume (numid=27)
Right: RX2 Digital Volume (numid=28)
Speaker volume:
RX3 Digital volume (numid=29)
Camcorder volume:
DEC6 Volume (numid=39)
Microphone volume:
DEC7 Volume (numid=40)
-----------------------------------------------
old OPs
-----------------------------------------------
2013-Jan-15
----------------
The creator of ALSAMixer updated it to correctly install for Nexus4. (Uninstall removes the app but the ALSA libraries remain on the phone.)
https://play.google.com/store/apps/details?id=com.skvalex.alsamixer&hl=en
Thank you so much!
--------
http://forum.xda-developers.com/attachment.php?attachmentid=1653124&d=1358438577
This is a piped output of "alsa_amixer -c 0 contents" from a stock Nexus 4 (4.2.1)
2013-Jan-13
-----------------
Is anyone successfully running ALSA on their Nexus 4?
If you do please share instructions to do so.
I am on stock 4.2.1(rooted/busybox) and I ran the AlsaMixer from
the Play Store but it doesn't seem to complete the installation.

http://forum.xda-developers.com/sho...ited Edition Kit★☆★ | aokp,minco,pa,rasbean |
Shameless promotion
Sent from my Nexus 4

Next you're going to tell me that you want systemd and PulseAudio on your device too, right?

I wiped to stock,
I installed AOKP-jb-mr1-build1,
then Nocturnal 1.4 LE for AOKP
and the ALSAMixer still doesn't work. It installs but I get the same blank screen with no settings.
What am I doing wrong?

I'm not sure what that app is, I just meant that some of the audio mods in the kit ROM referred to ALSA audio libs.
As you can tell I'm not the expert, sorry if that's not what you were referring too
Sent from my Nexus 4

I am looking for a way to control the audio stream parameters in particular the gain of the microphone.
Somebody suggested using ALSA and I'm trying get it going.

-Mindroid- said:
I am looking for a way to control the audio stream parameters in particular the gain of the microphone.
Somebody suggested using ALSA and I'm trying get it going.
Click to expand...
Click to collapse
I have only a Nexus 7, and the SoC is different from the Nexus 4, but look for alsa_amixer (installed by AlsaMixer) from within a console and execute
"alsa_amixer -c X contents" (without the quotes)
where X is one of the card numbers shown in your /proc/asound directory (e.g. card0 [X=0], card1 [X=1], etc). In my case, X=1 is the actual card where (a lot of) values can be set. One of those values is called "ADC Boost Gain"(I guess a programmable analog gain?).
I established a call with CSipSimple and successfully raised that parameter by 24dB in mid-call by executing "alsa_amixer -c 1 cset numid=20 2" [the default value was 0 and each step increases the level by 12dB]
You can query individual parameters by executing alsa_amixer -c X cget numid=Y
YMMV with the Nexus 4. Good luck!

Thank you! This looks really promising.
I only have "card0" aka [apq8064tablasnd].
When trying to execute "alsa_mixer -c 0 contents" I get an error stating that I'm missing
library "libasound.so". Any ideas what could be wrong?

I'm not sure whether libasound.so came with the AlsaMixer app. If it did you may need to copy the library into a system library path, e.g. /system/lib. If not, I could send you the library that I have. I actually forgot whether I found the library somewhere online or whether I cross-compiled it myself...
Sent from my Nexus 7 using xda app-developers app

ALSA on Nexus 4 sound capabilities
ALSAMixer in the Play Store was updated to support Nexus 4. See OP.
---------------------------------------------------------------
The attached file is the output of running
alsa_amixer -c 0
I'm new to ALSA and have trouble figuring out which one is the microphone gain control.

I have installed this app but unfortunately I don't know how to completely uninstall it help please?:thumbup:
..sent from space.

amarb70 said:
I have installed this app but unfortunately I don't know how to completely uninstall it help please?:thumbup:
..sent from space.
Click to expand...
Click to collapse
If I understand correctly the app is just an installer that puts the ALSA libraries on your system.
If you are not using them it probably doesn't matter if they are there or not. You can contact the app creator about it.

-Mindroid- said:
ALSAMixer in the Play Store was updated to support Nexus 4. See OP.
---------------------------------------------------------------
The attached file is the output of running
alsa_amixer -c 0
I'm new to ALSA and have trouble figuring out which one is the microphone gain control.
Click to expand...
Click to collapse
Post the output of
alsa_amixer -c 0 contents
Any labels containing "ADC gain" or "Boost" would be prime candiates

amarb70 said:
I have installed this app but unfortunately I don't know how to completely uninstall it help please?:thumbup:
..sent from space.
Click to expand...
Click to collapse
Restore your back up
Sent from my Nexus 4 using xda premium

alsa_amixer c- 0 contents
chdloc said:
Post the output of
alsa_amixer -c 0 contents
Any labels containing "ADC gain" or "Boost" would be prime candiates
Click to expand...
Click to collapse
Thank you for being so patient with me!
I'm such a Linux noob. It took me forever to figure out that I need 'su' to do anything.
I will update the OP to link to this file.

-Mindroid- said:
Thank you for being so patient with me!
I'm such a Linux noob. It took me forever to figure out that I need 'su' to do anything.
I will update the OP to link to this file.
Click to expand...
Click to collapse
Holy smokes! This is one complicated mixer! And I've seen many.
It may help in narrowing choices down by you capturing another
alsa_amixer -c 0 contents
while you are on a call and look at the diffs. While you do that (being on a call, but don't run anything else that may use audio such as music playback apps) also report the output of
cat /proc/asound/card0/pcm0p/sub0/status
to make sure that phone calls are actually routed through ALSA. Anything but "CLOSED" is good.
I do not have a Nexus 4 so I cannot help trying to find the best parameters for a given application. The app ALSAMixer should help I would think.
Does this program now actually display anything?

chdloc said:
Holy smokes! This is one complicated mixer! And I've seen many.
It may help in narrowing choices down by you capturing another
alsa_amixer -c 0 contents
while you are on a call and look at the diffs. While you do that (being on a call, but don't run anything else that may use audio such as music playback apps) also report the output of
cat /proc/asound/card0/pcm0p/sub0/status
to make sure that phone calls are actually routed through ALSA. Anything but "CLOSED" is good.
I do not have a Nexus 4 so I cannot help trying to find the best parameters for a given application. The app ALSAMixer should help I would think.
Does this program now actually display anything?
Click to expand...
Click to collapse
It's a long shot but if you are in the New York tri-state area I wouldn't mind meeting up and letting you mess around with the Nexus4.
The invitation is open to anyone with ALSA experience. I would love to learn more about it first-hand.
As far as I can tell:
- ALSAMixer installs the ALSA libraries and displays the control set. I tried modifying a value with it and it didn't work.
It's a matter of wrong syntax I think, I will contact the app creator about it.
- Terminal Emulator works. I was able to change the value of "AUX_PGA_LEFT Volume" with the following command:
alsa_amixer cset numid=54 39
I'm not sure what this one does yet but I will investigate later today.
- unfortunately, during a phone call "proc/asound/card0/pcm0p/sub0/status" (playback) as well as
"proc/asound/card0/pcm0c/sub0/status" (capture) report "closed". Earlier I tried recording a voice call from an app
and trying to prepare an audio stream with MediaRecorder.AudioSource.VOICE_CALL throws an exception.
- when recording an audio stream with MediaRecorder.AudioSource.MIC and CAMCORDER
"proc/asound/card0/pcm0c/sub0/status" reports audio stream parameters. I'm attaching the piped output of
"alsa_amixer -c 0 contents" during a voice call, recording with mic and recording with camcorder.

-Mindroid- said:
[...]
- when recording an audio stream with MediaRecorder.AudioSource.MIC and CAMCORDER
"proc/asound/card0/pcm0c/sub0/status" reports audio stream parameters. I'm attaching the piped output of
"alsa_amixer -c 0 contents" during a voice call, recording with mic and recording with camcorder.
Click to expand...
Click to collapse
This is fun...
There is certainly a difference between the "idle" set of parameters you had posted earlier and the ones that you took during a voice call.
I found some good information that explains the parameters here
https://github.com/psykick5/android_device_lge_mako/blob/master/snd_soc_msm_2x_Fusion3
Try to change numid=48 (i.e. 'ADC1 Volume') and numid=40 (i.e. 'DEC7 Volume'); these two parameters should change the microphone level, provided automatic gain control does not compensate for the changes.
(It bothers me, though, that the range of values shown by alsa_amixer and the ones shown in the above link don't match)
Make sure that the changes stick by issuing
alsa_amixer cget numid=X
For phone calls I would certainly change numid=65 (i.e. 'TX6 HPF cut off') from 0 (apparently really only a DC offset filter) to 2 (apparently a high-pass filter with a cutoff frequency of 150Hz), which would be good enough for HD voice.

chdloc said:
This is fun...
There is certainly a difference between the "idle" set of parameters you had posted earlier and the ones that you took during a voice call.
I found some good information that explains the parameters here
https://github.com/psykick5/android_device_lge_mako/blob/master/snd_soc_msm_2x_Fusion3
Click to expand...
Click to collapse
Great find! This seems to be exactly what we need.
Most intriguing there are also facilities for Voice Call and FM Radio audio streams. Those are not currently working on
the Nexus4 at the moment and this might shed some light on a possible solution.
I find some of their nomenclature confusing. They use "TX" for recording and "RX" for playback.
Also they seem to set values twice - :1:0 for turn off and :1:1 for turn on. Do I have to issue commands twice?
I confirmed with 'cget' that I am indeed setting values with 'cset'.
chdloc said:
Try to change numid=48 (i.e. 'ADC1 Volume') and numid=40 (i.e. 'DEC7 Volume'); these two parameters should change the microphone level, provided automatic gain control does not compensate for the changes.
(It bothers me, though, that the range of values shown by alsa_amixer and the ones shown in the above link don't match)
Make sure that the changes stick by issuing
alsa_amixer cget numid=X
Click to expand...
Click to collapse
It seems that DEC7 controls to the MICROPHONE stream and DEC6 the CAMCORDER.
I will focus my attention on these.
chdloc said:
For phone calls I would certainly change numid=65 (i.e. 'TX6 HPF cut off') from 0 (apparently really only a DC offset filter) to 2 (apparently a high-pass filter with a cutoff frequency of 150Hz), which would be good enough for HD voice.
Click to expand...
Click to collapse
I was wondering about that myself. There is very bad low frequency noise on video recordings so I will
definetly look into this.

-Mindroid- said:
I find some of their nomenclature confusing. They use "TX" for recording and "RX" for playback.
Click to expand...
Click to collapse
Actually, the nomenclature is quite common, TX, i.e. transmit [to the network] denotes the signal to be transmitted (taken from from microphone)
while RX is the receive signal [from the network] to be played back through a loudspeaker.
-Mindroid- said:
Also they seem to set values twice - :1:0 for turn off and :1:1 for turn on. Do I have to issue commands twice?
Click to expand...
Click to collapse
No, you will have to issue the command only once. Without having looked at the underlying code I tend to think that the first number denotes the type, i.e. integer vs string, and the second number the actual value.
Another interesting observation is that the SoC of the Nexus 4 seems to support SRS TruMedia via an effects mixer, which reportedly has potential to improve audio considerably (http://www.srstechnologies.com/content.aspx?id=1269 , I believe).

Record Japanese FM Radio band with stock app!!

Probably of limited interest to the few of us in Japan with international Galaxy Note 2's who are also interested in recording FM Radio. I've found a bit of a roundabout way of doing so using the stock app.
I am in Japan, so the current stock FM app doesn't natively tune to Japan's FM band (76-90 Mhz). I started looking into the feasibility of tweaking the current FM radio app to scan for the Japanese band instead of only the Americas/European band, or look into tweaking an Xposed module or something. I installed the very old Galaxy S Radio Widget Location selector, and it works like a charm on my Galaxy Note II.
While I could have probably flashed the old FMradio app from the Galaxy S, I was more interested in tweaking the new one from the Galaxy Note II as it has FM recording built in. For anyone thinking 'try Spirit FM' I've bought it and use it and it works well. But it would still be nice to have the stock software tweaked to work on the Japanese FM band.
Now that I've discovered the old FM widget works, I was able to tune to local stations here in Japan. Then I open the FM Radio app and I'm able to not only save the scanned Japanese stations- I was even able to record using the current stock FM Radio app!! It's just what I was hoping would happen.
There are a few issues though:
-I still can't use the FM Radio app itself to tune in to those stations. I first have to tune to them using the widget, but once they're tuned in, I can record using the app!
-for some reason, the wav files I've recorded via the FM Radio app don't seem to play back quite right in any of my music apps. For example, I made a 4 minute recording from one station. It plays back perfectly fine in the FM Radio app itself. But when I try to play it in the stock music app, winamp, or recforge, it only shows up as 4 seconds long. The file is a full-size 44100Hz, 16-bit stereo recording (47mb). Not sure why it's not playing back in the other programs.
Anyway, it's not perfect, but much better than I expected! I can now listen to and record FM Radio using the stock app here in Japan!
I'm not software-development-level technically inclined, so if anyone with any know how is interested, the widget developer posted the source code on his blog back when he first created it. That was about 3 years ago, so the link to the source is dead now... but hopefully interest in this project isn't!
It would be great if we could get a tweak for either the widget to manually tune to stations and record, or the FM Radio app itself to tune to the 76-90 mHz band!

I've made a little progress with the stock FM Radio app. I can now tune to the Japanese FM band in program (without the widget).
The way I accomplished this is by adding these Csc features to /system/csc/feature.xml :
Code:
<!-- SEC FMRadio -->
<CscFeature_FMRadio_FrequencySpaceAs>50</CscFeature_FMRadio_FrequencySpaceAs>
<CscFeature_FMRadio_DefaultChannelAs>76.0</CscFeature_FMRadio_DefaultChannelAs>
<CscFeature_FMRadio_DisableRTPlusInfo>false</CscFeature_FMRadio_DisableRTPlusInfo>
<CscFeature_FMRadio_DeconstantAs>50</CscFeature_FMRadio_DeconstantAs>
<CscFeature_FMRadio_BandWidthAs>76000_90000</CscFeature_FMRadio_BandWidthAs>
I found these features here and adjusted them to the Japanese Band.
Honestly, I don't know what all FrequencySpaceAs or DeconstantAs features mean. If anyone knows, please share.
By entering these values, we can now scan through the Japan FM band range and record. There is a caveat though. It seems the buttons were programmed to not allow scanning for stations LOWER than 87.5 mhz. If you happen to be on 87.5, you can press the back button once and it will take you to the next available lower station (in my case 85.1), but after that, you can't use the back button. You can only use the forward scan button until it circles back around to the lower end of the band (in my case 76.5).
Again, It's not a huge deal and it doesn't hinder you from now finding stations on the Japanese band. But it would be better if both buttons could be used freely. Also, the programmed station buttons also won't tune to any station under 87.5. You can program any station you pick up onto the buttons, but when you press them they don't work.
I really would love to get some people's input who know more about this. Where would the 87000 minimum value for the back button and program buttons be placed? Would it be in an xml file or a smali file?
Also the first time I recorded, I'm almost sure it was a .wav file. But yesterday, it output a .m4a file. Any idea how or why this changed? Any idea how I might change the output file format/quality? Any idea how I might expand the settings menu?
I know this is in the general section where probably most devs don't really look, but I would REALLY appreciate some insight or input on this. Thanks for listening!

I did it!
...made more progress that is.
I figured it out. I decompiled the stock app and changed some of the smali code. And now I've managed to natively access Japanese FM bands in the stock app!!! There are still a few things I need to work out, such as when pressing the saved stations button, it still doesn't tune to the station if it's under 87.5. My next aim is to get those buttons working.
Also, the widget now tunes to programmed stations, even if they're in the Japan range. But the display will not show anything lower than 87.5. So I'll be working on that too.
I'll post my modded file(s) in a new thread in the apps forum. Hopefully then it can get a bit more exposure and input. This thread will just serve as a starting point. This is a system app, so you must be rooted to install. To install it, I simply uninstalled the stock app via Titanium Backup. Then using Root Explorer I copy this apk to the system/app directory, mount R/W, rename to FmRadio.apk, and restart. That should do it! You can now tune to bands below 87.5!
UPDATE: You can find the new thread and modded apk here.

[MOD] Native SIP/VOIP Calls on Moto X

Hello
I always prefer native support than third party software if it is possible. Unfortunately on our Moto X function SIP/VOIP is blocked, so for VOIP calls we must install better or worse third party software. I discovered that the solution is very simple. All we need is to modify one xml file. Of course this solution is only for rooted phones and I test it only on my Moto X (XT1052) with stock KitKat 4.4.2, however I think that should works on any variant of Moto X.
Well...short guide
- In your root file manager browse to /system/etc/permission
- open to edit file android.software.sip.xml and search for:
Code:
<permissions>
<feature name="android.software.sip" />
</permissions>
- then add additional line and finally you should have:
Code:
<permissions>
<feature name="android.software.sip" />
<feature name="android.software.sip.voip" />
</permissions>
That's it. Save file and reboot.
After reboot you should see additional option in dialer settings

Are you saying this enables built-in VoIP calling without the aid of third party apps/software?

titetanium said:
Are you saying this enables built-in VoIP calling without the aid of third party apps/software?
Click to expand...
Click to collapse
Yes, exactly.

testuser0072 said:
Hello
I always prefer native support than third party software if it is possible. Unfortunately on our Moto X function SIP/VOIP is blocked, so for VOIP calls we must install better or worse third party software. I discovered that the solution is very simple. All we need is to modify one xml file. Of course this solution is only for rooted phones and I test it only on my Moto X (XT1052) with stock KitKat 4.4.2, however I think that should works on any variant of Moto X.
Well...short guide
- In your root file manager browse to /system/etc/permission
- open to edit file android.software.sip.xml and search for:
Code:
<permissions>
<feature name="android.software.sip" />
</permissions>
- then add additional line and finally you should have:
Code:
<permissions>
<feature name="android.software.sip" />
<feature name="android.software.sip.voip" />
</permissions>
That's it. Save file and reboot.
After reboot you should see additional option in dialer settings
Click to expand...
Click to collapse
NICE FIND, bud.
Great work!!! :good:

Trying it on my XT1060

It's a known modification but unfortunately not enough. SIP is really enabled but it is pretty useless due to the annoying voice distortion on the other side of communication. It appears as high-frequency harmonic distortion and disfigures your voice beyond every acceptable level. I've put a lot of effort to resolve the problem but so far without any significant success. The main question is why dedicated sip applications can operate more or less without distortion and native sip can't. The best guess is that native sip (voip) is not managed as telephony function but rather as one of special audio functions. Therefore it lacks acoustic echo cancellation functionality. Or other possibility might be that pretty high latency of native voip is responsible that echo cancellation simply can't "grab". I tried to replace or repair files responsible for voip and general audio, even drivers but without any luck. It must be that the whole problem is somehow connected to radio and baseband management. Hence it would be very interesting to know if voip distortion appears only in MOTOX or in other phones as well. I assume that it is a Google issue but you never totally know before you try it. It may be connected to Motorola baseband configuration solely.
By the way, I was really exited when I read that one of malfunctions supposed to be repaired among hundreds others in Google 4.4.3 release would be internet telephony (voip). Now I'm on stock 4.4.4 and no progress regarding sip was made....

piskr said:
It's a known modification but unfortunately not enough. SIP is really enabled but it is pretty useless due to the annoying voice distortion on the other side of communication. It appears as high-frequency harmonic distortion and disfigures your voice beyond every acceptable level. I've put a lot of effort to resolve the problem but so far without any significant success. The main question is why dedicated sip applications can operate more or less without distortion and native sip can't. The best guess is that native sip (voip) is not managed as telephony function but rather as one of special audio functions. Therefore it lacks acoustic echo cancellation functionality. Or other possibility might be that pretty high latency of native voip is responsible that echo cancellation simply can't "grab". I tried to replace or repair files responsible for voip and general audio, even drivers but without any luck. It must be that the whole problem is somehow connected to radio and baseband management. Hence it would be very interesting to know if voip distortion appears only in MOTOX or in other phones as well. I assume that it is a Google issue but you never totally know before you try it. It may be connected to Motorola baseband configuration solely.
By the way, I was really exited when I read that one of malfunctions supposed to be repaired among hundreds others in Google 4.4.3 release would be internet telephony (voip). Now I'm on stock 4.4.4 and no progress regarding sip was made....
Click to expand...
Click to collapse
Well...what can I say...I am not a VOIP expert, but I tested built-in VOIP for a some short calls (2 different SIP/VOIP accounts) and seems to be OK. Distortion level is minimal and for me acceptable and really don't know if it is not dependent from SIP/VOIP operator, because I had similar results on Cyanogen roms, where overall VOIP working or I always thought that working

testuser0072 said:
Well...what can I say...I am not a VOIP expert, but I tested built-in VOIP for a some short calls (2 different SIP/VOIP accounts) and seems to be OK. Distortion level is minimal and for me acceptable and really don't know if it is not dependent from SIP/VOIP operator, because I had similar results on Cyanogen roms, where overall VOIP working or I always thought that working
Click to expand...
Click to collapse
That's really interesting. Distortion should appear on the other side. No one complained about robotic hardly understood voice when you called?
I tested voip with CM too and the results were the same or even worst (no audio at all). But then, I thought that radio and baseband was not replaced during CM installation and that's why voip wasn't improved.
Anyway, believing that voip operator is responsible for audio distortion is an easy solution but the facts are against it. Using dedicated sip applications removes distortion completely. Besides my operator uses standard codecs G711 alaw and ulaw which are also integrated into the system. And I could use native voip on my previous phone with JB quite normally (besides greater latency which was caused by a weak processor).
Really hard to understand where is the reason that I can't use native sip normally.

piskr said:
That's really interesting. Distortion should appear on the other side. No one complained about robotic hardly understood voice when you called?
Click to expand...
Click to collapse
Of course other side complain sometimes, but overall they understood my voice, which is indeed slightly robotic.
piskr said:
I tested voip with CM too and the results were the same or even worst (no audio at all). But then, I thought that radio and baseband was not replaced during CM installation and that's why voip wasn't improved.[...].
Click to expand...
Click to collapse
I mean other than Moto X phones (Some HTC and Huawei) with CM, where VoIP works OK. So far I didn't install CM on my Moto X, so I can't say nothing about results.
piskr said:
Really hard to understand where is the reason that I can't use native sip normally
Click to expand...
Click to collapse
However I use VoIP from time to time, but I agreed, what is a real reason that we can't use native sip normally ?

piskr said:
That's really interesting. Distortion should appear on the other side. No one complained about robotic hardly understood voice when you called?
I tested voip with CM too and the results were the same or even worst (no audio at all). But then, I thought that radio and baseband was not replaced during CM installation and that's why voip wasn't improved.
Anyway, believing that voip operator is responsible for audio distortion is an easy solution but the facts are against it. Using dedicated sip applications removes distortion completely. Besides my operator uses standard codecs G711 alaw and ulaw which are also integrated into the system. And I could use native voip on my previous phone with JB quite normally (besides greater latency which was caused by a weak processor).
Really hard to understand where is the reason that I can't use native sip normally.
Click to expand...
Click to collapse
Same experience here, the receiving end could not understand me. Using pbx in a flash and Vitelity trunks.

piskr said:
voip distortion appears only in MOTOX or in other phones as well.
Click to expand...
Click to collapse
I've tried VOIP at work on many different phones, native. All have bugs to distortion, echo, delay, fail to wake, fail to roam. Disappointing.

How to improve audio with Viper4Android (Root required; tested only on Lollipop)

The other day I went looking for an audio DSP to use on my Shield Tablet running Lollipop. I came upon some posts recommending "Viper4Android" and went looking for a away to install it.
Here's my instructions, adapted from this article: http://www.droidviews.com/guide-viper4android-make-work-lollipop-lrx21o/
Download "TestLolliViPER_v2.3.3.0.zip" from this post (pre-Lollipop users can download ViPER4Android FX from the official thread and install the APK, skip ahead to step 5)
Change to permissive mode with SELinux Mode Changer from the Play Store (required for Lollipop, maybe for KitKat too)
Enable developer options and uncheck "Use Nuplayer" (Lollipop only)
Reboot to recovery and flash the zip you downloaded; reboot back to Android
Open Viper4Android and let it download its drivers (reboot required)
Open Viper4Android and under settings switch "FX Compatible" mode to "Compatible"
FX compatibility mode caused most apps to not use V4A. Leave it on the "Normal" setting instead.
Specific apps:
For PowerAmp, enable MusicFX under Settings > Audio > Advanced Tweaks, turn on "Tone/Volume". Also, switch off the Equ, Tone and Limit under Tone/Volume
For GoneMad Music Player, select "Use External DSP" under Preferences > Audio > Equalizer
Spotify appears to just work now.
Effects:
Turning on "Speaker Optimization" makes the Shields' speakers sound less tinny
Try some IRS files to imitate/replicate various bass boost, etc effects from various manufacturers
Alternatively, try some headphone correction filters (these attempt to flatten the frequency response of your headphones, making music sound the way musicians really intended it to sound)
See also the explainations for all of the settings.
I hope this works for other people. Tell me if I've made a mistake or left something out.

Thanks! will give this a try soon, what about boosting volume? I haven't seen anything for boosting volume yet in lollipop

Folks will discover this after clicking the first link: this solution requires Root. I've heard great things about Viper, and if you have your device unlocked and rooted, give it a go.

jaredmorgs said:
Folks will discover this after clicking the first link: this solution requires Root. I've heard great things about Viper, and if you have your device unlocked and rooted, give it a go.
Click to expand...
Click to collapse
Oh right, thanks for that. I keep forgetting that not everyone has root access and a custom recovery
And even though I've been reading XDA for years, I've only written a few posts.

genicles said:
Thanks! will give this a try soon, what about boosting volume? I haven't seen anything for boosting volume yet in lollipop
Click to expand...
Click to collapse
Yes, there is the "Extra Loud" option, with three strength levels.

Does this method work with Spotify? I don't think you can change audio settings via the app and don't these V4A instructions only apply on an app by app basis?

I've tried this and it doesn't appear to have any effect on the sound on my shield. Followed instructions exactly but makes no difference to sound quality regardless of what player I use.
Sent from my SHIELD Tablet using Tapatalk

mossief1965 said:
I've tried this and it doesn't appear to have any effect on the sound on my shield. Followed instructions exactly but makes no difference to sound quality regardless of what player I use.
Sent from my SHIELD Tablet using Tapatalk
Click to expand...
Click to collapse
Try playing with the settings--specifically the NUplayer toggle and the settings in PowerAmp (if you're using it). In most guides for Lollipop for V4A, it says to turn off NUplayer. But for some reason, on my other device (a G3 with CM12), I need NUplayer on. I don't have to use compatible mode on it either.
It's a stretch, especially since the OP tested his steps on this device, but I don't think it'll hurt.

sixstringedmatt said:
Does this method work with Spotify? I don't think you can change audio settings via the app and don't these V4A instructions only apply on an app by app basis?
Click to expand...
Click to collapse
I just had a try with Spotify and it seems to work with no changes required. It even opens V4A when selecting 'equalizer' in settings, so it appears to be quite aware of external DSPs.
Soundscape also has no settings for audio, but doesn't go through V4A. I don't know what to do about that, besides complaining to the company.
Sent from my SHIELD Tablet using XDA Free mobile app

... making music sound the way musicians really intended it to sound ...
Click to expand...
Click to collapse
There is so much wrong with that I don't know where to start LOL (but this is not meant to be any sort of observation on the app itself).
But ya know, whatever sounds good in the end

diji1 said:
There is so much wrong with that I don't know where to start LOL (but this is not meant to be any sort of observation on the app itself).
But ya know, whatever sounds good in the end
Click to expand...
Click to collapse
I was referring to Beat's claim that their bass-heavy headphones make your music sound the way the musicians wanted it to. Tyle from Inner Fidelity (who has tested many headphones with a pretty sophisticated setup) has said:
I would think most recording studios in the world use a curve called "flat." That way they know what they're hearing on the monitors is what's going onto the disc. The Audio Engineering Society is filled with engineers who write papers and learn about how to achieve a flat and neutral audio response, and then design and build the gear that goes into recording studios. I've measured four of the Beats full-size headphones, and a handful of their in-ear models, and they deviate significantly from flat.
Click to expand...
Click to collapse
The headphone correction files I linked to attempt to flatten the response of each headphone, making them sound more like professional-grade studio monitors (speakers) or headphones.

The V4A mod sounds great, but it seems to break streaming audio to the Shield Controller.

after Ota 3.1 upgrade Viper is not working anymore

[ROM] Lenovo_P2_MIUI10_8.6.19 trial version

Official introduction:
The new design with the "full screen" as the core
New full-screen gestures that belong to the full-screen era of fingertip operation
The new system UI to comprehensively visualize and respond to the "full screen" inside and outside
(Not a full-screen user, the visual upgrade is also clear at a glance)
Naturally pleasant sound system
Natural and changing system sounds, nice and funny
System sound reduction and notification filtering strategies greatly reduce sound interruptions
Built-in natural white noise, forest, ocean, summer night, fire, and drizzle to help you relax and sleep
Dynamic wake-up ring tone, changing style with weather and time, and placing a sweet vocal broadcast
Powerful voice AI
"Little love students" and MIUI deep integration, a word to get the phone complex operation
Small love training program to create and share your unique skills
Exploratory full-voice driving mode: Wechat, call, navigation, and song
AI blessing, faster than faster
Significant improvement in system handiness and smoother operation of typical scenes
IoT Internet, more convenient and more open
Negative Information Assistant Adds Smart Home Cards for More Efficient Device Management
Proactively reminds you when connected to a connected device and connects in the fastest possible step
Millet IoT and its smart chain brand smart appliances gradually access
Other optimization and adjustment
Portal 2.0 to further enrich and expand identifiable content; new translation, AI mapping capabilities
Picture quality AI optimization, applying clear magic to low quality pictures of today's headlines and circle of friends
New optimization of system tools such as clocks and notes
system
Fix the problem that the shutdown alarm has a low probability of failure in the off state of charge
Fix WeChat Small Video Even No Sound Problem
Fix face unlock failure/slow success rate
Portal
Add portal setting entry from "Settings - MIUI Lab" to "Settings - More Settings"
Millet Wallet
Add Xiaomi bus can check the current post-sale bus card progress function in Settings->MiMi account->Payment information->My bus card
Added Xiaomi Public Bus Cards to Display Default Bus Card Balance Function
Work:
RIL (telephone, SMS, 4G , VOLTE)
fingerprint
WIFI
Bluetooth
camera
Recording
Video playback
Audio frequency
sensor
flashlight
led
GPRS
FM
DT2W
Fingerprint gesture
Known BUG:
NFC
Languages: English and Chinese
Download:https://mega.nz/#F!uQF3WKIK!6iKFang66GHj9kSpruCbkw

Good work dude.....

This is lit????
?????Awesome work man
Really only one bug??????
By the way one small question,Can we flash it on p2A42???

Portrait works in camera?

couldnt signin to playstore
play store is black could not signin.

just one question portrait mode work??

Fast charging works?

Volte works????

Anyone install it?

For heck sakes guys stop asking "has anyone tested" "is blah blah blah working" and just go try yourself and inform others here

b50corei5 said:
For heck sakes guys stop asking "has anyone tested" "is blah blah blah working" and just go try yourself and inform others here
Click to expand...
Click to collapse

Android nought :/ i want oreo

yourmine20 said:
Android nought :/ i want oreo
Click to expand...
Click to collapse
There's plenty of Oreo roms here
Go look yourself

Anandabasak said:
Portrait works in camera?
Click to expand...
Click to collapse
I cant find portrait mode in camera
advaithbhat said:
play store is black could not signin.
Click to expand...
Click to collapse
Use google installer 3.0 for miui, play store work but cant sync google contacts
rahulrj.rj566 said:
just one question portrait mode work??
Click to expand...
Click to collapse
shwetangb said:
Fast charging works?
Click to expand...
Click to collapse
I think it doesnt work. 5v 2a only.
One bug: Auto brightness is not working. It will decrase to minimum value

Thanks a lot Dev! MIUI 10 looks awesome.

no official release rom for lenovo P2 base on Oreo. Nougat is the last update release for this device.

b50corei5 said:
There's plenty of Oreo roms here
Go look yourself
Click to expand...
Click to collapse
Ik i currently on oreo but i want emui Android oreo build

Anyone tried this ROM...?? Can give a review

is it for model P2c72 or P2a42 version ?

Suvam Mondal said:
is it for model P2c72 or P2a42 version ?
Click to expand...
Click to collapse
C72