Jump to content

Requests for Hi-Res Support (please state which build of Poweramp you are using)


Recommended Posts

  1. Samsung Galaxy S10+, Exynos
  2. LineageOS 18.1 official beyond2lte nightly from 2022-01-19 (lineage_beyond2lte-userdebug 11 RQ3A.211001.001 10038599)
  3. worked on stock (Samsung One UI), Hi-Res Output screen shows "Variant: Samsung UHQA PCM" but shows "Failed: Hi-Res Output" when playing a song and reverts to OGL ES output.
  4. detection log posted below
  5. I checked the folders listed and couldn't find a file matching the description, possibly because running LineageOS.

 

04:28:02.673 build-911-arm64-play
Device: samsung samsung SM-G975F lineage_beyond2lte exynos9820 "exynos9820" beyond2lte lineage_beyond2lte-userdebug 11 RQ3A.211001.001 10038599 [arm64-v8a, armeabi-v7a, armeabi]

samsung
FLAG_VARIANT_SAMSUNG_UHQA
OLD changelist=
USB can handle Hi-Res - sdk=30
OK flags=0x136108600000000
FLAG_VARIANT_SAMSUNG_UHQA
FLAG_SUPPORTS_UNITY_GAIN_STREAM
FLAG_SUPPORTS_USB
FLAG_NEEDS_EXTRA_SLEEPS
FLAG_SUPPORTS_SPEAKER
FLAG_OUT_PARAMS_UNDETECTABLE
FLAG_SUPPORTS_LDAC
FLAG_DLFCN
FLAG_STOP_FOR_PAUSE
INTERNAL_OUTPUT_FLAG_SR_384K
INTERNAL_OUTPUT_FLAG_SR_352K
INTERNAL_OUTPUT_FLAG_SR_192K
INTERNAL_OUTPUT_FLAG_SR_176K
INTERNAL_OUTPUT_FLAG_SR_96K
INTERNAL_OUTPUT_FLAG_SR_88K

Link to comment
Share on other sites

  • 2 weeks later...
  • Replies 1.6k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

On 1/1/2022 at 10:20, andrewilley said:

Questo è generalmente qualcosa che dipende dal dispositivo. Alcuni hardware (o più precisamente, il firmware) consentono variazioni casuali, mentre altri no.

In generale, le ROM Android Samsung gestiscono i loro percorsi di uscita audio utilizzando accoppiamenti bloccati. Quindi le frequenze fino a 96 hKz inclusi forzeranno l'uscita a 16 bit, le frequenze fino a 192 kHz utilizzeranno 24 bit e qualsiasi altra cosa al di sopra utilizza 32 bit. Dato che stai utilizzando un dispositivo Samsung, questo è il comportamento che dovresti aspettarti.

A quanto ho capito, la decodifica interna e l'elaborazione all'interno del codice di PA (ad esempio per le operazioni di equalizzazione) sono generalmente comunque più elevate (Floating, 64/32 bit).

Andre

Andre thank you very much for your reply. But in my humble opinion I think it would be a great thing to separate the bits from the sample rate. My device easily supports 24 bits, but by setting this value on Poweramp it automatically goes to 192 khz and you no longer hear anything. I believe I have found that some programs similar to yours allow bit / khz separation. But I think your program is excellent. By inserting this change it would become a perfect program. I hope that in the future the 24 bits can be set independently. Thanks again

Link to comment
Share on other sites

  • 1 month later...

 

Version Info ======================

Build: Poweramp Equalizer build-932-bundle-play full verified cached

Store: Play

Arch: 64

Skin: ActivityTheme_Black

Device: OPPO CPH2123 oppo6779 OP4C51L1 CPH2123 [arm64-v8a, armeabi-v7a, armeabi]

Installer: com.android.vending (29.8.13-21 [0] [PR] 435704331)

Android: 11 OPPO/CPH2123/OP4C51L1:11/RP1A.200720.011/1646411009679:user/release-keys es

Link to comment
Share on other sites

  • 1 month later...
  • 5 weeks later...
On 5. 4. 2016 at 15:25, maxmp said:

Vaše zařízení podporuje Hi-Res audio _ výstup_* (alespoň  24bit , vzorkovací frekvence alespoň 96 kHz ), ale Poweramp v3.0 alpha to nepodporuje?
Požádejte o podporu zde!

Uveďte (žádosti bez těchto položek budou smazány):

  1. Model zařízení
  2. Verze ROM (verze pro Android, sklad/OTA/Vlastní ROM):  /system/build.prop soubor nebo výstup adb shell getprop
  3. Proč si myslíte, že vaše zařízení podporuje Hi-Res (odkaz na funkce zařízení atd.)?
  4. U nejnovějších sestavení Powerampu, snímek obrazovky Nastavení / Zvuk / Pokročilá vylepšení / Protokoly detekce zvukových výstupů.
  5. Užitečná může být kopie souboru /etc/audio_policy.conf  nebo audio_output_policy.conf  nebo audio_io_policy.conf  vašeho zařízení  . [na některých zařízeních to lze nalézt v /vendor/etc/ nebo  /system/etc/  místo toho] 

Upozorňujeme, že toto je pro  požadavky na výstup ve vysokém rozlišení , pouze přehrávání (s převzorkováním) zvuku ve vysokém rozlišení je již implementováno pomocí Poweramp v2.0 pro všechna zařízení/ROM.

Honor 7A android 8

Link to comment
Share on other sites

 Hi-Res Support request for OPPO RENO 7 5G

Dimensity 900 (can play in Hi-res, can select any sample rate available - 192khz, 96khz, 48khz, 44.1khz - but the output only stays at 48khz.

 

Here's the Log:

09:08:37.776 build-939-uni

Device: OPPO OPPO CPH2371 CPH2371T2 oplus6877 "mt6877" OPD4A1L1 CPH2371_11_A.14 [arm64-v8a, armeabi-v7a, armeabi]

 

mt6877 is_mtk

FAILED to read=/vendor/etc/audio_output_policy.conf

FAILED to read=/vendor/etc/audio_io_policy.conf

FAILED to read=/system/etc/audio_policy.conf

reading=/vendor/etc/audio_policy.conf

has outputs_primary, sampling_rates=44100|48000|96000|192000

has outputs/primary formats=AUDIO_FORMAT_PCM_32_BIT|AUDIO_FORMAT_PCM_16_BIT

has usb

has usb outputs

has usb_device, sampling_rates=dynamic

has usb formats=dynamic

forcing FLAG_VARIANT_MTK_HIFI

USB can handle Hi-Res - sdk=30

OK flags=0xd24001c00000000

FLAG_VARIANT_MTK_HIFI

FLAG_FORCE_PCM_8_24

FLAG_SUPPORTS_USB

FLAG_SUPPORTS_FLT_DYN_RANGE

FLAG_SUPPORTS_LDAC

FLAG_DLFCN

INTERNAL_OUTPUT_FLAG_SR_192K

INTERNAL_OUTPUT_FLAG_SR_96K

INTERNAL_OUTPUT_FLAG_SR_48K

INTERNAL_OUTPUT_FLAG_SR_44K

Screenshot_2022-06-15-09-07-21-52_345bb2134bfb84a7decceb0b36861421.jpg

Link to comment
Share on other sites

On 1/25/2022 at 11:45 AM, spaceyavin said:
  1. Samsung Galaxy S10+, Exynos
  2. LineageOS 18.1 official beyond2lte nightly from 2022-01-19 (lineage_beyond2lte-userdebug 11 RQ3A.211001.001 10038599)
  3. worked on stock (Samsung One UI), Hi-Res Output screen shows "Variant: Samsung UHQA PCM" but shows "Failed: Hi-Res Output" when playing a song and reverts to OGL ES output.
  4. detection log posted below
  5. I checked the folders listed and couldn't find a file matching the description, possibly because running LineageOS.

 

04:28:02.673 build-911-arm64-play
Device: samsung samsung SM-G975F lineage_beyond2lte exynos9820 "exynos9820" beyond2lte lineage_beyond2lte-userdebug 11 RQ3A.211001.001 10038599 [arm64-v8a, armeabi-v7a, armeabi]

samsung
FLAG_VARIANT_SAMSUNG_UHQA
OLD changelist=
USB can handle Hi-Res - sdk=30
OK flags=0x136108600000000
FLAG_VARIANT_SAMSUNG_UHQA
FLAG_SUPPORTS_UNITY_GAIN_STREAM
FLAG_SUPPORTS_USB
FLAG_NEEDS_EXTRA_SLEEPS
FLAG_SUPPORTS_SPEAKER
FLAG_OUT_PARAMS_UNDETECTABLE
FLAG_SUPPORTS_LDAC
FLAG_DLFCN
FLAG_STOP_FOR_PAUSE
INTERNAL_OUTPUT_FLAG_SR_384K
INTERNAL_OUTPUT_FLAG_SR_352K
INTERNAL_OUTPUT_FLAG_SR_192K
INTERNAL_OUTPUT_FLAG_SR_176K
INTERNAL_OUTPUT_FLAG_SR_96K
INTERNAL_OUTPUT_FLAG_SR_88K

 

Link to comment
Share on other sites

  • 4 weeks later...
  • Device model : ASUS ROG phone 6 AUSU-AI2201(HK)
  • ROM version : Stock
  • Why do you think your device supports Hi-Res (link to device features, etc.): Hi-Res Audio up to 384 kHz / 32-bit for 3.5mm output
  • cant find the  /etc/audio_policy.conf ...

14:34:29.996 build-939-bundle-play
Device: asus asus ASUS_AI2201_F WW_AI2201 taro "qcom" ASUS_AI2201 SKQ1.220406.001.WW_Phone-32.2810.2206.95-0 release-keys [arm64-v8a, armeabi-v7a, armeabi]

taro is_snapdragon
FAILED to read=/vendor/etc/audio_output_policy.conf
FAILED to read=/vendor/etc/audio_io_policy.conf
FAILED to read=/system/etc/audio_policy.conf
FAILED to read=/vendor/etc/audio_policy.conf
forcing FLAG_DLFCN FLAG_NEEDS_DEEP_BUFFER FLAG_NEEDS_EXTRA_SLEEPS
USB can handle Hi-Res - sdk=32
FLAG_VARIANT_USB_ONLY
OK flags=0x474601400000000
FLAG_VARIANT_USB_ONLY
FLAG_SUPPORTS_USB
FLAG_SUPPORTS_FLT_DYN_RANGE
FLAG_NEEDS_EXTRA_SLEEPS
FLAG_SUPPORTS_LDAC
FLAG_DLFCN
FLAG_NEEDS_DEEP_BUFFER
FLAG_ALLOW_DVC_EFFECT
FLAG_BT_DVC_EFFECT
INTERNAL_OUTPUT_FLAG_SR_192K
INTERNAL_OUTPUT_FLAG_SR_176K
INTERNAL_OUTPUT_FLAG_SR_96K
INTERNAL_OUTPUT_FLAG_SR_88K

 

Screenshot_20220723-014846_Poweramp.jpg

Getprop.txt

Link to comment
Share on other sites

  • 1 month later...
On 3/22/2021 at 2:32 AM, yjpiaomiao said:

1.Sony Wlakman NW-A105

2.Andriod9 Sony Custom ROM V4.02

3.This is a HiFi Player powered by Android

4.Poweramp Build900

It could be play on 192khz but only 16bit in Audio Track Output.There is no Hi-Res option and the OpenSL ES Hi-Res Output could only be used on USB DAC and BT.

Hope you can help solve this problem.

Same here.

Link to comment
Share on other sites

Same problem as was mentioned above: HI-Res output is available for BT and USB DAC only.

1. Xiaomi 12s Ultra

2. MIUI 13 by Xiaomi.EU 13.0.8 Stable, Android 12

3. HI-Res Audio + HI-Res Audio Wireless certified. Snapdragon 8+ Gen 1

4. Poweramp build-942-bundle-play 

Outputs detection log:

18:17:56.817 build-942-bundle-play
Device: Xiaomi Xiaomi 2203121C thor taro "qcom" thor SKQ1.220303.001 release-keys [arm64-v8a, armeabi-v7a, armeabi]

taro is_snapdragon
FAILED to read /vendor/etc/audio_output_policy.conf
FAILED to read /vendor/etc/audio_io_policy.conf
FAILED to read /system/etc/audio_policy.conf
FAILED to read /vendor/etc/audio_policy.conf
MIUI=13
USB can handle Hi-Res - sdk=31
FLAG_VARIANT_USB_ONLY
OK flags=0x404001400000000
FLAG_VARIANT_USB_ONLY
FLAG_SUPPORTS_USB
FLAG_SUPPORTS_FLT_DYN_RANGE
FLAG_SUPPORTS_LDAC
INTERNAL_OUTPUT_FLAG_SR_192K
INTERNAL_OUTPUT_FLAG_SR_176K
INTERNAL_OUTPUT_FLAG_SR_96K
INTERNAL_OUTPUT_FLAG_SR_88K
 

Audio policies attached in Vendor.zip, keeping folder structure.

While 12S Ultra is mentioned as TARO in outputs detection log, probably Vendor\etc\audio\sku_taro_qssi\audio_policy_configuration.xml should be actually used.

Vendor.zip build.prop output_detection.log

Link to comment
Share on other sites

  • 2 weeks later...
  • 4 weeks later...

1. Infinix Hot 10 X682C

2. Android 10 (Build No. X682C-H694CD-Q-GL-220729V366)

3. My device has MTK Hi-FI. It worked before I updated the app from build 941 to build 944, but rolling back to 941 doesn't fix it. The sampling rate is locked at 48khz even if I choose 192khz.

4. Detection Log is posted below.

5. The audio_policy.conf is also posted below.

 

310269471_3325017504425310_1405440524334577629_n.jpg

audio_policy_configuration.xml

Link to comment
Share on other sites

It works on AAudio output when I downgrade to build 941, but on the latest version it doesn't. Note that in AAudio output, updating to the latest version makes the bit depth locked on 32 bit. Downgrading to build 941 makes it 24 bit and I can use 192khz sampling rate.

I think it's because both AAudio and Hi-Res output became locked on 32 bit depth. My phone might be included in those devices where the bit depth is paired with the sample rate, because back when I can use Hi-Res output with 192khz, my bit depth is locked on 24 bit.

 

Edited by Crimson
slight clarification
Link to comment
Share on other sites

  • 1 month later...

Hello, Poweramp can't handle my new SONY Android Walkman, NW-WM1AM2  in Hi-Res Audio Support (Internal DAC). I wish I could.

Audio Log as follows.

08:15:34.960 build-945-bundle-play
Device: SonyAudio Sony NW-WM1AM2 icx1298_000 icx1298 "icx1298" icx1298 1.03.00 [arm64-v8a, armeabi-v7a, armeabi]

FAILED to read /vendor/etc/audio_output_policy.conf
FAILED to read /vendor/etc/audio_io_policy.conf
FAILED to read /system/etc/audio_policy.conf
FAILED to read /vendor/etc/audio_policy.conf
USB can handle Hi-Res - sdk=30
FLAG_VARIANT_USB_ONLY
>>>OK flags=0x404001400000000
FLAG_VARIANT_USB_ONLY
FLAG_SUPPORTS_USB
FLAG_SUPPORTS_FLT_DYN_RANGE
FLAG_SUPPORTS_LDAC
INTERNAL_OUTPUT_FLAG_SR_192K
INTERNAL_OUTPUT_FLAG_SR_176K
INTERNAL_OUTPUT_FLAG_SR_96K
INTERNAL_OUTPUT_FLAG_SR_88K
 

Link to comment
Share on other sites

  • 4 weeks later...

Честь STF-L09 

 

дерсия гражданская
9. 1.
Версия Android
9
 
Процессор
Хисиликон Кирин 960
БАРАН
4,0 ГБ
 
Прошивка модуля связи
21С30Б323С007С000,21С30Б
323S007C000
4.9.148
Версия ядра
android@localhost #1
Ср, 23 июня, 13:16:43 CST 2021
Сборка
 943
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...