[Sound Eq]

So I am trying to understand again things here, so on my galaxy s7 edge with exynos dac I installed on it v4a and poweramp alpha and in its settings I made chose high res 192/24 output but when I check the driver status in v4a it shows 48000

I thought that v4a processes what ever is being output

Any feedback on this is appreciated

 

[abm0]

in its settings I made chose high res 192/24 output but when I check the driver status in v4a it shows 48000

I thought that v4a processes what ever is being output

In what scattered discussions I've seen of this I see that people keep referring to a device-default sampling rate being the only one supported by V4A, typically 48k or 44.1k. But at the same time if I look back to /system/etc/audio_policy.conf on my phone I see that the primary outputs are explicitly set to only use "44100|48000". So maybe try to use a file editor with root permissions to edit the sampling_rates field in the ... primary{ outputs{ primary{ ... } and low_latency{ ... } sections and set it to 44100|48000|96000|192000 in both places, then reboot and see if that works.
 
Of course, use your own judgement on how you want to manage the risks of fiddling with system files. When I went into this kind of thing I first made a copy of the original audio_policy.conf on my SD card and I knew I could always use it to overwrite the modified one via TWRP (recovery mode) even if my system became un-bootable due to the modifications. (Then again Android would have to be some kind of incredibly crappy system for some changes to an audio device configuration file to make the entire system fail to boot.)

 

[Sound Eq]

  In what scattered discussions I've seen of this I see that people keep referring to a device-default sampling rate being the only one supported by V4A, typically 48k or 44.1k. But at the same time if I look back to /system/etc/audio_policy.conf on my phone I see that the primary outputs are explicitly set to only use "44100|48000". So maybe try to use a file editor with root permissions to edit the sampling_rates field in the ... primary{ outputs{ primary{ ... } and low_latency{ ... } sections and set it to 44100|48000|96000|192000 in both places, then reboot and see if that works.
 
Of course, use your own judgement on how you want to manage the risks of fiddling with system files. When I went into this kind of thing I first made a copy of the original audio_policy.conf on my SD card and I knew I could always use it to overwrite the modified one via TWRP (recovery mode) even if my system became un-bootable due to the modifications. (Then again Android would have to be some kind of incredibly crappy system for some changes to an audio device configuration file to make the entire system fail to boot.)

I dont see the low latency in the audio-policy.config is that a problem?
 
in the primary output i only see 48000
 
so in general what are the chances that if i modify as you suggested in the primary that the device will not boot after i modify it

 

[abm0]

  I dont see the low latency in the audio-policy.config is that a problem?

Not sure. I just saw it in other discussions and on my phone and I figured V4A might be going through there instead of the primary-primary, in attempts to keep latency low even as it offers you extra processing. If your audio works without that section, then just focus on the primary output settings.
 

so in general what are the chances that if i modify as you suggested in the primary that the device will not boot after i modify it

Realistically I'd say pretty slim, hardly worth mentioning even (but I mentioned them anyway to cover my bases). At worst you might lose all audio output until you change it back and reboot. I fiddled around with all 3 settings under usb_device through several reboots and nothing significant happened except when V4A started working with my external DAC when I nailed the right settings. Since you'd be messing with the primary output and not just the USB, you may lose all audio output if it doesn't work as hoped, but I wouldn't expect anything worse than that and I wouldn't expect it to be unrecoverable.

 

[abm0]

 in its settings I made chose high res 192/24 output but when I check the driver status in v4a it shows 48000

This just in: the V4A driver itself is limited to 48000, so only the developers can fix this.

 

[Sound Eq]

Well there in v4a they don't believe in high res audio

 

[abm0]

Well there in v4a they don't believe in high res audio

According to the local rules I can't comment on that since this thread is not in the Sound Science forum.

 

[Sound Eq]

  According to the local rules I can't comment on that since this thread is not in the Sound Science forum.

​you can send me your reply by pm

 

[ljnew]

No problem gents, glad to help!!

Didn't realize that was my 4000th...damn, time flies. Feels like yesterday I joined this joint.

Thanksvapman!

I'm using v4a and uapp for every song i have to turn v4a on and off to get it to work. I'm using lgv20. How do I fix?

 

[dracinn]

I'm using v4a and uapp for every song i have to turn v4a on and off to get it to work. I'm using lgv20. How do I fix?

Do you still have any problems?

 

[ljnew]

Do you still have any problems?

Yes, same problems.

Also Tidal skips

 

[dracinn]

What root solution do you use I use Magisk and this is my setup