Database Users

[Q] Straight Answer on CIQ

I'm assuming that, for the most part, the apps on the Market that are designed to "discover" CIQ or traces of it are going to look for any small thing that might be left over from the removals, regardless of whether or not it's actually still part of our ROMs. That said, for all our devs who've put out ROMs that claim to not have CIQ on board, how do we know for sure that it's been removed?
Case in point - I'm currently running ACS ICS v5, and every ACS release that I've been on has claimed to have CIQ removed - yet, I ran 4 different CIQ discovery apps on a whim this morning, and they all claimed to find Carrier IQ on board. Is it just hype, or have we been missing something all along?
/and by "we," I mean, all the devs who work way harder on this stuff than me
//is basically just a ROM slut

From what I've read, the CIQ code is still baked into the kernel. BUT because the guts of CIQ were removed, the code has nothing to talk to.
That may be the culprit being detected. If you are getting other "false positives" then post screen shots of your output.

I am running SRF 1.2 still and from the OP for that ROM states that it is completely removed, not disabled or partitially removed.
"What's the secret sauce? Carrier IQ, the infamous Sprint spyware package, has been completely removed! More details in the second post - you won't believe what we found! Themers and other mod developers take note, many modifications were made to the system in order to achieve this exclusive feature."
When I run Voodoo CIQ app it says.
Carrier IQ has been found and is active
Detection score: 370
Test for: Android logcat debugging log
(LOGCAT, weight 100)
found: I/ActivityManager( 2840): Start proc android.iqd for broadcast android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver: pid=9960 uid=1000 gids={3003, 3002, 3001, 1015, 1006}
found: I/ActivityManager( 2840): Start proc android.iqd for broadcast android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver: pid=9960 uid=1000 gids={3003, 3002, 3001, 1015, 1006}
found: I/ActivityManager( 2840): Start proc android.iqd for broadcast android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver: pid=9960 uid=1000 gids={3003, 3002, 3001, 1015, 1006}
found: D/ ( 9960): onReceive Intent { act=com.sprint.android.SPRINTEXTENSION_STARTED cmp=android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver }
found: D/ ( 9960): onReceive Intent { act=com.sprint.android.SPRINTEXTENSION_STARTED cmp=android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver }
Test for: ROM binaries and daemons
(SYSTEM_BINARIES, weight 70)
found: /system/bin/iqmsd
found: /system/lib/libiq_client.so
Test for: Running processes
(RUNNING_PROCESSES, weight 200)
found: system 9960 2376 213724 14076 ffffffff 00000000 S android.iqd
Test for: Suspicious classes
(SUSPICIOUS_CLASSES, weight 0)
found: com.carrieriq.iqagent.service.receivers.BootCompletedReceiver

Yeah, I guess Voodoo is the one I hadn't run yet - according to that, I'm in the clear:
Voodoo Carrier IQ Detector report:
Build fingerprint:
sprint/SPH-D700/SPH-D700:2.3.5/GINGERBREAD/EI22:user/release-keys
Carrier IQ elements found
− however it seems inactive
Detection score: 170
Test for: Linux kernel interfaces
(KERNEL_INTERFACES, weight 50)
nothing found
Test for: Android logcat debugging log
(LOGCAT, weight 100)
found: I/ActivityManager( 285): Start proc android.iqd for broadcast android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver: pid=2073 uid=1000 gids={3002, 3001, 1015, 1006, 3003, 1001}
found: I/ActivityManager( 285): Start proc android.iqd for broadcast android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver: pid=2073 uid=1000 gids={3002, 3001, 1015, 1006, 3003, 1001}
found: I/ActivityManager( 285): Start proc android.iqd for broadcast android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver: pid=2073 uid=1000 gids={3002, 3001, 1015, 1006, 3003, 1001}
found: D/ ( 2073): onReceive Intent { act=com.sprint.android.SPRINTEXTENSION_STARTED cmp=android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver }
found: D/ ( 2073): onReceive Intent { act=com.sprint.android.SPRINTEXTENSION_STARTED cmp=android/com.carrieriq.iqagent.service.receivers.BootCompletedReceiver }
found: I/ActivityManager( 285): No longer want android.iqd (pid 2073): hidden #16
Test for: Linux kernel drivers
(KERNEL_DRIVERS, weight 50)
nothing found
Test for: System services
(SERVICES, weight 70)
nothing found
Test for: ROM binaries and daemons
(SYSTEM_BINARIES, weight 70)
found: /system/bin/iqmsd
found: /system/lib/libiq_service.so
found: /system/lib/libiq_client.so
Test for: ROM configs
(ETC_CONFIG, weight 0)
nothing found
Test for: Packages
(PACKAGES, weight 70)
nothing found
Test for: Running processes
(RUNNING_PROCESSES, weight 200)
nothing found
Test for: Suspicious classes
(SUSPICIOUS_CLASSES, weight 0)
found: com.carrieriq.iqagent.service.receivers.BootCompletedReceiver
Test for: Linux kernel dmesg log
(DMESG, weight 100)
nothing found

Mine had a score of 170 and then re-ran it to show someone that mine is inactive and then the score jumped to 370 and said active. I'm thinking wtf...

when creating the CIQ mod, k0nane had to leave certain directories in order for things to work. They're completely empty of the files that were in them, but their existence will register on the voodoo app until supercurio and k0nane fine tune the detection. CIQ is removed from your phone it you're running a CIQ-free rom. This is says the yellow warning that elements may still exist but CIQ may not be present.

The Root said:
when creating the CIQ mod, k0nane had to leave certain directories in order for things to work. They're completely empty of the files that were in them, but their existence will register on the voodoo app until supercurio and k0nane fine tune the detection. CIQ is removed from your phone it you're running a CIQ-free rom. This is says the yellow warning that elements may still exist but CIQ may not be present.
Click to expand...
Click to collapse
/thread 10char

I trust Konane a lot more than some random app. He is the one that warned us all about this and has made sevetal phones ciq free.
Sent from my Epic on Legend or my Galaxy Tab rooted (feels naked without a ROM)

lancelane said:
I trust Konane a lot more than some random app. He is the one that warned us all about this and has made sevetal phones ciq free.
Sent from my Epic on Legend or my Galaxy Tab rooted (feels naked without a ROM)
Click to expand...
Click to collapse
As do I, believe me. I'm new on the boards, but I've been lurking for at least a year now, and I've never had any reason to doubt our devs' fine work Like I said, I mostly tried out those detection apps on a whim, since I had no reason to believe that CIQ was still active on my ROMs (and obviously it's been a current event of sorts) and it just kind of threw me for a loop when I got the results that I did. Anyway, thanks to the community for such quick answers, hopefully I didn't come off as too hostile in my first post!

rekrdskratcher said:
As do I, believe me. I'm new on the boards, but I've been lurking for at least a year now, and I've never had any reason to doubt our devs' fine work Like I said, I mostly tried out those detection apps on a whim, since I had no reason to believe that CIQ was still active on my ROMs (and obviously it's been a current event of sorts) and it just kind of threw me for a loop when I got the results that I did. Anyway, thanks to the community for such quick answers, hopefully I didn't come off as too hostile in my first post!
Click to expand...
Click to collapse
You must not have read the disclaimer on the app. It says it may report false positives still.

[KB-Article] Troubleshooting Bluetooth Issues on LineageOS 14 devices

Note: This post summarizes the experiences I had when fixing Bluetooth on the sltexx device.
Even though parts of the following are device specific some fixes may also be ported to other device overlays after testing.
Also the shared audio HAL in android_harware_samsung might be used by other devices.
Please do not use this thread to report any issues you are having on your device. This is an advisory for fellow developers only!!
Short description of known Bug Reports:
1) Some BT features are not working, such as: Receiving files, Bluetooth tethering, OBEX, etc.
Reported as: BUGBASH-653
Affects: Bluetooth.apk
Devices: Possibly all, but caused by a rare condition, port to your device if neccesary​2) The phone does not connect to cars / bt-headsets using the hands-free profile for calling
Reported as: BUGBASH-308
Affects: Bluetooth.default.so
Devices: Possibly all Devices with WBS=off in combination with bt-device relying on WBS​3) The phone connects, media working, but in-call sound is completely garbled or muted on both ends
Reported as: BUGBASH-302 / BUGBASH-264
Affects: build.prop, libbt-vendor.so, Bluetooth.default.so, audio.primary.universal5430.so
Devices:
a) Samsung devices using qualcomm HAL msm8974 (klte)
b) Samsung devices using android_hardware_samsung audio HAL (sltexx, and devices with: TARGET_AUDIOHAL_VARIANT := samsung, see list in 3rd post)
c) Samsung devices using qualcomm HAL msm89** (jfltexx)​
4) While connected to bt-headset systems sound such as volume change and ringtone are played on speaker and headset simultaneously.
Reported as: none, fixed internally
Affects: mixer_paths_0.xml
Devices: sltexx specific, maybe other Samsung behave similar​
Detailed background description and fixes in next post….

1) Description: https://jira.lineageos.org/browse/BUGBASH-653
Background: The registration of the "EMAIL Message Access" Service seems to be faulty.
The MAP: MSE MAS Email Instance Support was added to CM14.1 but not CM13!
https://github.com/LineageOS/androi...mmit/819847bb7f72a69a7d7fc662bcd37625247fceec
There is also a switch to disable all new non-aosp bt data features:
https://github.com/LineageOS/androi...mmit/96a55efb0edac3c2af523f938b338dd16d4f8ac4
However it might be useful to fix the originating issue which I assume is the SDP registration of those features: -> No one has checked this until now..
Fix: https://review.lineageos.org/#/c/177998/
2) Description: https://jira.lineageos.org/browse/BUGBASH-308
Background: The BMWs (and probably other cars also) check the available codecs first:
Code:
BTA_AG_AT_BAC_EVT /* avablable codec */
and expect the wide-band speech [WBS] profile. Because that is not enabled on compile level the BMW sends a BTA_AG_CLOSE_EVT.
The connection is terminated and phone_state_change tries to continue with an invalid idx because the SLC connection is already down.
If you look at the logcat of the motog closely, you can find the following:
Code:
bt_btif : btif_hf_upstreams_evt: event=BTA_AG_WBS_EVT
audio_hw_primary: adev_set_parameters: enter: bt_wbs=on
Therefore the build must have been compiled with: BTM_WBS_INCLUDED
Code:
#if (BTM_WBS_INCLUDED == TRUE )
#define BTA_AG_WBS_EVT 31 /* SCO codec info */
#endif
Fix: https://review.lineageos.org/#/c/177996/
NOTE: If you are experiencing mute calls or garbled incall sound after this, continue with 3a/3b depending on your device
3a) Description: Garbled /mute incall sounds on bluetooth (msm8974)
Background:
The sample rate for calls is usually 8k, however for wide-band speech it is 16k. It seems that some devices cannot handle this sample rate and will only work on WBS with 8k.
This behavior was confirmed on the klte. The fix might be ported to other devices:
Fix: https://review.lineageos.org/#/c/178371/
3b) Description: Garbled /mute incall sounds (Universal HAL)
Background: Unlike the klte, many Exynos devices have a shared audio HAL that supports 16k WBS however there was a small misuse of the sample rate constant resulting in garbled sound.
The usage of audio_hal.force_voice_config = (wide or narrow) is usually not required (add if needed)
If the fix from 3a has been applied or was previously set, remove any definitions of SCO_WBS_SAMPLERATE in the vendor config.
Fix: https://review.lineageos.org/#/c/182054/
Right now this in in testing. We are looking for more affected devices that are using android_hardware_samsung as audio HAL.
Update: See the detailed list of possible affected devices below, as far as I see all of them have not yet enabled WBS yet.
3c) Description: Garbled /mute incall sounds on bluetooth (msm89** / jfltexx)
 @jorgemiguel4 Found out what fixes the mute calls: Thanks to you!
#define BTM_WBS_INCLUDED TRUE
#define BTIF_HF_WBS_PREFERRED FALSE //With this set to TRUE there is no sound on my side.
Click to expand...
Click to collapse
This will enable WBS (for the car support) but it will use the default codec instead which does not have the WBS samplerate issue.
Therefore audio quality might not be perfect but at least it works.
4) Description: Ringer & notification sounds through headset and speaker
Background:
When pressing volume up/down buttons or on incoming calls the sound is played on both headset and speaker which seems to be an odd behaviour. This is not only for bluetooth, also for wired headsets and headphones. The issue seems to be quite old and some might say it works as designed: https://forum.xda-developers.com/showthread.php?t=2320446
However as this is a custom firmware we can change the corresponding audio routes!
Fix: https://github.com/Harinus/android_...mmit/f104a3d9775e6c6cfdfbb6e61f16b036d207c18b (will need modification for other devices)
Wrote this with my best knowledge and belief. If there is any incorrect information, please let me know.
Special thanks to @akk29, @side and everyone on webchat, gerrit and jira who provided help/logs

Collection of all TARGET_AUDIOHAL_VARIANT := samsung Devices I could find on github!
sltexx ...........Samsung Galaxy Alpha / SM-G850F....... [exynos5430]
#LineageOS/
noblelte-common ..Samsung Galaxy Note 5................. [exynos7420]
zero-common ......Samsung Galaxy S6..................... [exynos7420]
k3gxx ............Samsung Galaxy S5 / SM-G900H.......... [exynos5422]
hero-common ......Samsung Galaxy S7 Edge................ [exynos8890]
gts2-common ......Samsung Galaxy Tab S2................. [exynos5433]
#others/
klimtlte .........Samsung Galaxy Tab S 8.4 / SM-T705.... [exynos5420]
ja3gxx ...........Samsung Galaxy S4 Exynos / GT-I9500... [exynos5410]
lt033g ...........Samsung Galaxy Note 10.1 3g / SM-P601. [exynos5420]
on5xelte .........Samsung Galaxy J5 Prime....... ....... [exynos7570]
zenlte-common ....Samsung Galaxy S6 Edge +.............. [exynos7420]
chagalllte .......Samsung Galaxy Tab S 10.5 / SM-T805... [exynos5420]
chagallltetmo ....Samsung Galaxy Tab S 10.5 / SM-T807T.. [exynos5420]
j7elte ...........Samsung Galaxy J7 / SM-J700........... [exynos7580]

. The usage of audio_hal.force_voice_config = (wide or narrow) is usually not required (add if needed)
If the fix from 3a has been applied or was previously set, remove any definitions of SCO_WBS_SAMPLERATE in the vendor config.
Click to expand...
Click to collapse
On code review I read ur the discussion with shevt regarding using "audio_half.force_voice_config". So using this line in build.prop will always force hal to use wideband or narrow whichever specified OR
But removing this line I believe will allow audio hal to decide wide band or narrow based on network. I may be wrong.
When shevt removed force.voice.config I assume audio hal may be using "pcm_config_voice_sco" and not "pcm_config_voice_sco_wb" in which has been defined .rate 8000 which may be causing the problem for shevt.
I just want to understand. I have seen in pcm_config_voice_sco_wb rate defined as "SCO_WB_SAMPLING_RATE". what is value passed when you define this. Is it .rate=16000 or .rate=0?

@Harinus hope you can help me
i have same issue on BUGBASH-96 but WPS didn't fix it
i have this lines on logcat :
Code:
08-12 13:40:24.866 6824 6861 D bt_btif : A2DP-CTRL-CHANNEL EVENT UIPC_RX_DATA_READY_EVT
08-12 13:40:24.866 6824 6861 D bt_btif : a2dp-ctrl-cmd : A2DP_CTRL_CMD_START
08-12 13:40:24.866 6824 6861 W bt_btif : btif_recv_ctrl_data: A2DP command A2DP_CTRL_CMD_START while AV stream is not ready
08-12 13:40:24.866 6824 6861 D bt_btif : ## a2dp ack : A2DP_CTRL_CMD_START, status 1 ##
08-12 13:40:24.866 6824 6861 D bt_btif : a2dp-ctrl-cmd : A2DP_CTRL_CMD_START DONE
08-12 13:40:24.866 371 6892 I bt_a2dp_hw: a2dp_command: A2DP COMMAND A2DP_CTRL_CMD_START DONE STATUS 1
08-12 13:40:24.866 371 6892 E bt_a2dp_hw: a2dp_command: A2DP COMMAND A2DP_CTRL_CMD_START error 1
08-12 13:40:24.866 371 6892 E bt_a2dp_hw: start_audio_datapath: Audiopath start failed (status -1)
08-12 13:40:24.877 371 6892 I bt_a2dp_hw: start_audio_datapath: state 3
08-12 13:40:24.878 371 6892 I bt_a2dp_hw: start_audio_datapath: state AUDIO_A2DP_STATE_STOPPED
08-12 13:40:24.878 371 6892 I bt_a2dp_hw: a2dp_command: A2DP COMMAND A2DP_CTRL_CMD_START
my device tree links : https://github.com/LG-K10

@macs18max
You basically got it right.
The HAL consists of 2 parts:
android_hardware_samsung (1, audio HAL)
android_hardware_broadcom_libbt (2, bluetooth RIL)
Both must handle the sampling rate of the incoming and outgoing audio streams.
For the WBS codec both 8k and 16k are valid by specification. Other codecs may use only 8k.
1) PCM Config / force_voice_config
The audio HAL (pcm config) uses 16k for WBS (after my fix) and 8k for the other codecs.
It decides which sample rate based on the wb_amr_type that it gets from the RIL.
When setting "audio_hal.force_voice_config" it overrides the wb_amr_type and therefore the samplerate of the pcm config.
(pcm_config_voice_sco_wb or pcm_config_voice_sco)
voice_session_init registers a RIL callback for WB. That wont be registered when "audio_hal.force_voice_config" is set at all. https://github.com/LineageOS/android_hardware_samsung/blob/cm-14.1/audio/voice.c#L444
2) SCO_WBS_SAMPLE_RATE
The value is used in hw_sco_i2spcm_config https://github.com/LineageOS/android_hardware_broadcom_libbt/blob/cm-14.1/src/hardware.c#L1516 and defines the sample rate on hw layer.
The values 0 and 1 are used. -> SCO_WBS_SAMPLE_RATE is a macro, documented here: https://github.com/LineageOS/androi...bt/blob/cm-14.1/include/bt_vendor_brcm.h#L262
3) Conclusion.
From what I experienced both values on RIL and HAL must be equal. Otherwise the audio will be garbled.
However some HALs (e.g. klte) seem to not support 16k, so we force 8k there.
Maybe it does not work for @ShevT without the line in build.prop because the wb-amr callback is not working properly on that device.
Can not answer that without a device for testing.
@erfanoabdi
The issue looks like something not related to WBS. Do you have a full log?

Harinus said:
@erfanoabdi
The issue looks like something not related to WBS. Do you have a full log?
Click to expand...
Click to collapse
tnx for reply
yeah, logcat attached
interested thing is i can see this error is passed by using prebuilt audio hals but still no sound :
Code:
A2DP COMMAND A2DP_CTRL_CMD_START DONE STATUS 0
i don't want to use prebuilt hals, need to find way for fixing this.

erfanoabdi said:
tnx for reply
yeah, logcat attached
interested thing is i can see this error is passed by using prebuilt audio hals but still no sound :
Code:
A2DP COMMAND A2DP_CTRL_CMD_START DONE STATUS 0
i don't want to use prebuilt hals, need to find way for fixing this.
Click to expand...
Click to collapse
The origin of the error is: https://github.com/LineageOS/android_system_bt/blob/cm-14.1/audio_a2dp_hw/audio_a2dp_hw.c#L569. android_hardware_bt is the bluetooth stack that has changed quite a lot for the last versions of android.
Your build config of the stack(https://github.com/LG-K10/android_device_lge_m216/blob/cm-14.1/bluetooth/bdroid_buildcfg.h) is using definitions that seem to be obsolete since Android M (and also Nougat)
Check the related motorola https://github.com/LineageOS/androi...mmit/69feab615584f2b8bf7f51c0fd12817181453e02 repository!
Some parameters were renamed:
Code:
BLUETOOTH_QCOM_SW -> BLUETOOTH_QTI_SW
BTC_INCLUDED -> BLE_VND_INCLUDED
The currently missing "BLE_VND_INCLUDED" enables several CTRL feature callbacks that seem to be related to: "A2DP_CTRL_CMD_START"
I suggest porting the current version from motorola with all its defines:
Code:
#define BLUETOOTH_QTI_SW TRUE
#define MAX_ACL_CONNECTIONS 7
#define MAX_L2CAP_CHANNELS 16
#define BLE_VND_INCLUDED TRUE
#define BT_CLEAN_TURN_ON_DISABLED TRUE
plus the WBS enabling..
Code:
#define BTM_WBS_INCLUDED TRUE /* Enable WBS */
#define BTIF_HF_WBS_PREFERRED TRUE /* Use WBS */
I can not guarantee that this will fix the issue, but it is surely a good idea to fix the parameters.

I posted a AOSP Bluetooth patch to the jira bugtracker under issue
https://jira.lineageos.org/browse/BUGBASH-717
And here is the xda thread where the dev built this patch...
https://forum.xda-developers.com/go...m-dark-rom-t3492150/post73199372#post73199372
...maybe helpful !?!

lulli1 said:
I posted a AOSP Bluetooth patch to the jira bugtracker under issue
https://jira.lineageos.org/browse/BUGBASH-717
And here is the xda thread where the dev built this patch...
https://forum.xda-developers.com/go...m-dark-rom-t3492150/post73199372#post73199372
...maybe helpful !?!
Click to expand...
Click to collapse
See my comment on jira.. For axon7 its clearly the WBS issue that has been described above.

On jfltexx got it working in my car with the following, hope it helps somebody
#define BTM_WBS_INCLUDED TRUE
#define BTIF_HF_WBS_PREFERRED FALSE //With this set to TRUE there is no sound on my side.
and
SCO_WBS_SAMPLE_RATE = 0 or SCO_WBS_SAMPLE_RATE = 1 //worked fine with both. 0=8Hhz and 1=16kHz

Harinus said:
See my comment on jira.. For axon7 its clearly the WBS issue that has been described above.
Click to expand...
Click to collapse
Yes you were right. Thanks a lot. We solved the issue on the Nexus 5 by setting
BTIF_HF_WBS_PREFERRED to FALSE

Using HFP several users of the herolte got distorted sound when calling. See regression 1194. The problem occurred after enabling WBS in LOS nightly. What has to be done to apply a workaround? Is it sufficient to change the build.prop? Issue is really annoying.

nostromo12 said:
Using HFP several users of the herolte got distorted sound when calling. See regression 1194. The problem occurred after enabling WBS in LOS nightly. What has to be done to apply a workaround? Is it sufficient to change the build.prop? Issue is really annoying.
Click to expand...
Click to collapse
LOS Version: lineage-14.1-20171018-nightly-herolte-signed
Baseband: G930FXXU1DQF1
Kernel version: 3.18.14-gadb2bc5
I have Samsung Galaxy S7 G930F running latest nightly and have the voice distortion issue.
audio_hal.force_voice_config = wide [This is default, I didn't change this]
---------- Post added at 01:30 PM ---------- Previous post was at 12:33 PM ----------
padraigdoran said:
LOS Version: lineage-14.1-20171018-nightly-herolte-signed
Baseband: G930FXXU1DQF1
Kernel version: 3.18.14-gadb2bc5
I have Samsung Galaxy S7 G930F running latest nightly and have the voice distortion issue.
audio_hal.force_voice_config = wide [This is default, I didn't change this]
Click to expand...
Click to collapse
I got it working on my S7 by changing to the following:
audio_hal.force_voice_config = narrow
The audio person on the other end says they can hear me fine, but I think the audio quality of the incoming voice isn't that great. The voice is very understandable, just not super clear.

I tested
audio_hal.force_voice_config = narrow
on herolte with same nightly , but older baseband G930FXXU1BPJG. But it did not work. There is absolutely silence. No dial tone. No partner voice. Nothing. I have sadly to go back to nightly 20170919.

I've got a problem with Bluetooth on my Note 4 with Lineage OS 14.1. I've paired my android wear watch with my phone and can receive notifications and data from apps on the phone, but the watch can't access the internet through the Bluetooth connection. It worked fine on my old Touchwiz ROM. Is this related to problem 1 or something else?

none of these are the problem I have, my problem is that bluetooth doesn't even turn on

@Harinus
I have got issues with Call Audio on zerofltexx (S6). We are using the common audio HAL. Well the issue is I have got a pair of Beats Solo 3 Wireless Headphones which require WBS for Calls. Media audio works great. However there is no call audio whatsoever. Now I have tried many of the fixes you mentioned in your previous posts and non have solved this issue. I have tried the prebuilt audio HAL on LineageOS and it works fine with these headphones. Even the one by @macs18max for the same device works. I will attach a log when making a call. I have BT WBS as ON but PREFERRED to FALSE when this log was taken.

LG G6
this is what bluetooth does on my LG G6: The phone connects, media working, but in-call sound is completely garbled or muted on the other end
No idea on how to fix this. Phone is rooted and has the nightly from 20180206 with the microG-Patch. Same issue with previous versions.
any help would be appreciated
thnx lemonskater

I have this exact problem...
I'm now looking for the "How To" push code or config changes to my device? In the thread, there are a couple of fixes to try, and some files... but I don't have a single clue about what to do with them, how to "install" those fixes on my LOS 15.1 Galaxy S7. Im guessing I need an app on my phone to run and apply the changes... but I didn't find exactly how to.
I'm an experienced Windows sys admin, but I'm a total N00b as when it comes to Android. I want to learn to exploit the maximum of my phone, but I gotta start by making it work normal again. Can you help me with this? I'm totally lost as how I can solve my Bluetooth problem with the thread linked a little earlier!
Thank you SOOOOO much for every bit of help you could provide me.

[PSA] You can output Hi-Res audio via internal DAC

I've found recently that in last alphas of Poweramp player you can output hi-res audio (up to 24bit/192khz supported by our chip ) directly via Snapdragon's DAC (to heaphones ). And it works! BUT!
It only works with stock Roms apparently, I've checked few Nougats, Sultan's cm13 and only stock cm13 worked....
If someone knows of any other Rom which works with this please let me know!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Most of my audio is high def, plus I have pair of so called "hi-res" heaphones , one of them are cheapo Xiaomi Hybrids Pro, and this stack really does make difference. I've left Viper and Co. for good when it comes to my music.

Small update, it works wih CM13 from jgcap So that's what I'm staying on for the time being

You have hi-res headphones...
Would you consider the Sony MDR-1000X NC Headphones as "hi-res" headphones?
I have those, would I notice a difference?

It's a known Poweramp bug that should be fixed in Poweramp's next update. Currently it doesn't support hires audio on any Nougat device.

To force it to use high res on nougat, install arise, then go to /etc/init.d/ and rename arisesound_disabled_setprop to arisesound_setprop. Install version 704 alpha of Poweramp (if you haven't already), and reboot. It should now work. If that doesn't work, make sure your rom supports init.d.

r0tati0n said:
You have hi-res headphones...
Would you consider the Sony MDR-1000X NC Headphones as "hi-res" headphones?
I have those, would I notice a difference?
Click to expand...
Click to collapse
They are indeed Hi-Res certified, and have specs to follow. With decent quality recordings you might, it depends on how good is your hearing too
f41lbl0g said:
To force it to use high res on nougat, install arise, then go to /etc/init.d/ and rename arisesound_disabled_setprop to arisesound_setprop. Install version 704 alpha of Poweramp (if you haven't already), and reboot. It should now work. If that doesn't work, make sure your rom supports init.d.
Click to expand...
Click to collapse
I'm systemless ( for Android Pay ) is there systemless Arise?
Edit. Seems that, there is. Now gotta figure whatt is it about and how to install, never used it before.
Edit2. Done [just core], it sorta works now? Outputs hires to Lenovo Hi-Fi which is what you meant I guess? Won't give me peace of mind though as it outputs only in 16 bit (coverting my 24 bit audio midway).
Edit3. Sound seems actually better with that solution, it's especially noticeable with bass , it seems to truly output to DAC, latencies are even shorter than with poweramp's qualcom mode, and it seems to enable FLT_EXTENDED_DYN_RANGE in DAC, which I'm all about obviously, and that's what would result in improved bass
( I can set my bass to brain drilling now and it stays stable/without any distortions, just ...wow )

Update, probably final. Although the ARISE trick allows for forcing Hi-res option, and output, from poweramp. (resulting in pleasant sound) it doesn't use DAC directly and goes through software chain resulting in 16/48 audio in the end.
It's easy to check through adb with "adb shell dumpsys media.audio_flinger"
Native DAC output on jgcap's CM
Code:
Output thread 0xac4fe000 type 4 (OFFLOAD):
Thread name: AudioOut_17
I/O handle: 23
TID: 6203
Standby: no
Sample rate: 96000 Hz
HAL frame count: 30720
HAL format: 0x1a000004 (pcm-24bit-offload)
HAL buffer size: 30720 bytes
Channel count: 2
Channel mask: 0x00000003 (front-left, front-right)
Format: 0x1a000004 (pcm-24bit-offload)
Frame size: 1 bytes
Pending config events: none
Output device: 0x8 (WIRED_HEADPHONE)
Input device: 0 (NONE)
Audio source: 0 (default)
Normal frame count: 30720
Last write occurred (msecs): 3
Total writes: 196
Delayed writes: 0
Blocked in write: yes
Suspend count: 0
Sink buffer : 0xae0bd000
Mixer buffer: 0xae203000
Effect buffer: 0xae083000
Fast track availMask=0xfe
Standby delay ns=1000000000
AudioStreamOut: 0xae122540 flags 0x31 (DIRECT|COMPRESS_OFFLOAD|NON_BLOCKING)
Stream volumes in dB: 0:-10, 1:-27, 2:-20, 3:-17, 4:-13, 5:-20, 6:0, 7:-27, 8:-21, 9:-96, 10:-17, 11:0, 12:0
Normal mixer raw underrun counters: partial=0 empty=0
1 Tracks of which 1 are active
Name Active Client Type Fmt Chn mask Session fCount S F SRate L dB R dB Server Main buf Aux Buf Flags UndFrmCnt
none yes 6160 6 1A000004 00000003 22 61440 A 3 96000 0 0 005BA520 0xae0bd000 0x0 0x000 45792
0 Effect Chains
And on Nougat with ARISE
Code:
Output thread 0xb6179000 type 0 (MIXER):
Thread name: AudioOut_15
I/O handle: 21
TID: 671
Standby: no
Sample rate: 48000 Hz
HAL frame count: 1920
HAL format: 0x1 (pcm16)
HAL buffer size: 7680 bytes
Channel count: 2
Channel mask: 0x00000003 (front-left, front-right)
Processing format: 0x1 (pcm16)
Processing frame size: 4 bytes
Pending config events: none
Output device: 0x8 (WIRED_HEADPHONE)
Input device: 0 (NONE)
Audio source: 0 (default)
Normal frame count: 1920
Last write occurred (msecs): 16
Total writes: 30172
Delayed writes: 0
Blocked in write: yes
Suspend count: 0
Sink buffer : 0xb617b000
Mixer buffer: 0xb5311000
Effect buffer: 0xb617d000
Fast track availMask=0xfe
Standby delay ns=3000000000
AudioStreamOut: 0xb6149348 flags 0x8 (DEEP_BUFFER)
Frames written: 57930240
Suspended frames: 0
Hal stream dump:
Thread throttle time (msecs): 1228
AudioMixer tracks: 0x00000003
Master mono: off
FastMixer not initialized
Stream volumes in dB: 0:-10, 1:-31, 2:-35, 3:-28, 4:-28, 5:-35, 6:0, 7:-31, 8:-25, 9:-96, 10:-28, 11:0, 12:0
Normal mixer raw underrun counters: partial=0 empty=0
2 Tracks of which 1 are active
Name Active Client Type Fmt Chn mask Session fCount S F SRate L dB R dB Server Main buf Aux Buf Flags UndFrmCnt
1 yes 29842 3 00000005 00000003 497 7688 A 3 96000 0 0 010FE000 0xb617b000 0x0 0x001 3844
0 no 29842 3 00000001 00000003 497 7688 I 0 96000 0 0 00000000 0xb617b000 0x0 0x000 0
0 Effect Chains
In the result I'll stay with the CM13 till next poweramp update. With direct DAC output battery lasts forever, and sound quality is impossible to beat with any current software tricks.
Better bass was only due to limiter in the chain, turning it on in poweramp results in same bass improvemnt.

WilderSu said:
I've found recently that in last alphas of Poweramp player you can output hi-res audio (up to 24bit/192khz supported by our chip ) directly via Snapdragon's DAC (to heaphones ). And it works! BUT!
It only works with stock Roms apparently, I've checked few Nougats, Sultan's cm13 and only stock cm13 worked....
If someone knows of any other Rom which works with this please let me know!
Most of my audio is high def, plus I have pair of so called "hi-res" heaphones , one of them are cheapo Xiaomi Hybrids Pro, and this stack really does make difference. I've left Viper and Co. for good when it comes to my music.
Click to expand...
Click to collapse
Hi Wilder,
Can you please tell me, in the latest build (Build 798, which JUST came out I'm told), is there an option to BYPASS Snapdragon/Android audio processing if there is a separate (and superior) DAC detected (either internal or external via cable or BT)?? USB Audio Player Pro has this feature, and I'm wondering if Poweramp does as well.
This option you're speaking of appears to only be for the Snapdragon DACs.
Thank you!!

RockStar2005 said:
Hi Wilder,
Can you please tell me, in the latest build (Build 798, which JUST came out I'm told), is there an option to BYPASS Snapdragon/Android audio processing if there is a separate (and superior) DAC detected (either internal or external via cable or BT)?? USB Audio Player Pro has this feature, and I'm wondering if Poweramp does as well.
This option you're speaking of appears to only be for the Snapdragon DACs.
Thank you!!
Click to expand...
Click to collapse
Just tested it, I'm on Lineage 15.1 and not only it doesn't offer DAC but under LOS it doesn't ever offer the new Hi-Res OpenSL option. So it's a massive regression. I'm not going to test it on old CM stock, it's just not worth it. If I remember correctly latets DU offered HI-Res OpenSL [no dac though] .
Dissapointing.

WilderSu said:
Just tested it, I'm on Lineage 15.1 and not only it doesn't offer DAC but under LOS it doesn't ever offer the new Hi-Res OpenSL option. So it's a massive regression. I'm not going to test it on old CM stock, it's just not worth it. If I remember correctly latets DU offered HI-Res OpenSL [no dac though] .
Dissapointing.
Click to expand...
Click to collapse
Hey Wilder,
Thanks for starting this thread.
Which version are you testing though? The official V2 of Poweramp does NOT have any of the features I mentioned, but the last V3 "Beta/Preview" version does.
They just THIS MORNING released the Beta Build 799 version, which eliminated ALL the bugs found on previous versions from what I understood. I feel V3 is coming VERY VERY soon based on these recent updates which have come faster than usual. (V2 came out April 2013 FYI lol). I would recommend going to Play Store, signing up for Beta on the Poweramp trial page in Play Store, and then when the update appears update it, and enjoy.
IF you do this, please try both the OpenSL ES Output and HI-Res Output options and see if you can determine which one actually DOES the bypassing in question (if either do). I think we both would like to know. lol
If not, that's fine too.
Also, this article (below) from 2 months ago that I found earlier today claims ALL the apps listed in it offer bypassing of Android audio, at least that's how I'm interpreting. It mentions an earlier build of the V3 Beta Poweramp, so the 799 will definitely be a stable version of it to try out. Check it out and let me know what you think too.
https://www.google.com/search?q=The...=chrome..69i57j69i65&sourceid=chrome&ie=UTF-8 (CHOOSE THE FIRST ONE TO SEE ARTICLE!)
Thanks either way!!

RockStar2005 said:
Hey Wilder,
Thanks for starting this thread.
Which version are you testing though? The official V2 of Poweramp does NOT have any of the features I mentioned, but the last V3 "Beta/Preview" version does.
They just THIS MORNING released the Beta Build 799 version, which eliminated ALL the bugs found on previous versions from what I understood. I feel V3 is coming VERY VERY soon based on these recent updates which have come faster than usual. (V2 came out April 2013 FYI lol). I would recommend going to Play Store, signing up for Beta on the Poweramp trial page in Play Store, and then when the update appears update it, and enjoy.
IF you do this, please try both the OpenSL ES Output and HI-Res Output options and see if you can determine which one actually DOES the bypassing in question (if either do). I think we both would like to know. lol
If not, that's fine too.
Also, this article (below) from 2 months ago that I found earlier today claims ALL the apps listed in it offer bypassing of Android audio, at least that's how I'm interpreting. It mentions an earlier build of the V3 Beta Poweramp, so the 799 will definitely be a stable version of it to try out. Check it out and let me know what you think too.
https://www.google.com/search?q=The...=chrome..69i57j69i65&sourceid=chrome&ie=UTF-8 (CHOOSE THE FIRST ONE TO SEE ARTICLE!)
Thanks either way!!
Click to expand...
Click to collapse
I'm on latest v3 and it doesn't work, checked 12.5 DU and RR 6 ROMs and it doesn't work there either, seems the dev just checks it against latest official stock which was 5.1.1 CM which sucks majorly.

WilderSu said:
I'm on latest v3 and it doesn't work, checked 12.5 DU and RR 6 ROMs and it doesn't work there either, seems the dev just checks it against latest official stock which was 5.1.1 CM which sucks majorly.
Click to expand...
Click to collapse
Ok I didn't understand like 90% of that. LOL But thanks anyway.
So you think it'll work on the official V3 then??
Uggh this means if I notice a difference (with bypass on vs. off) I'd have to use UAPP. But I like Poweramp more, damm*t!!!!!! LOL

RockStar2005 said:
Ok I didn't understand like 90% of that. LOL But thanks anyway.
So you think it'll work on the official V3 then??
Uggh this means if I notice a difference (with bypass on vs. off) I'd have to use UAPP. But I like Poweramp more, damm*t!!!!!! LOL
Click to expand...
Click to collapse
Don't think it will, unless enough users will spam their forum about this phone. It's just too old, no one cares anymore.

WilderSu said:
Don't think it will, unless enough users will spam their forum about this phone. It's just too old, no one cares anymore.
Click to expand...
Click to collapse
Hmm ok.
What about that article? It claims it can do it though?

Wasn't there a DAC enabler for Snapdragon Chipsets in Magisk Manager?
There is aptX HD available through Bluetooth on Oreo ROMS and newer.
I don't know if it works on Nougat or below though as I'm not an audiophile.

Deleted

[ROM][12.1][LAUREL_SPROUT] PixelPlusUI [OFFICIAL] [Twelve][AOSP]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
"This is a user-friendly thread, all your suggestions, and proper bug reports are important to us but don't be disrespectful to anyone here. Your suggestions and proper bug reports will be taken into consideration.."
PixelPlusUI is another aftermarket AOSP ROM Minimal UI & close to Stock Android ROM. What differentiates us from the rest, you ask? LET'S FIND OUT. It has additional localized and personalized functionality while preserving the stock Android look by adhering to Material Design guidelines. Unlike OEMs' slow and untimely updates, we closely follow Google to bring the latest updates to our users, and even prolonging support to devices that have been declared obsolete by OEMs. Our ROMs' source code is open-source, secure, stable, and outstanding. Your experience using PixelPlusUI will be butter smooth with added convenience and features. The main aim of this form is to give the user a better experience without compromising the quality of the Android experience so that no one struggles with any kind of difficulties while using their device. PixelPlusUI brings a better UI/UX to Android with a seamless experience coupled with customizations and user security. In short, it's perfectly balanced between Great Performance, Security, Stability, Minimal UI & Awesome features including pixel goodies But this doesn't mean we aim to provide all the customization available on the planet. So do not hesitate anymore, join us now and start enjoying the beauty of stock Android. Download and enjoy PixelPlusUI on your respective devices!
- Kostya Maslennikov - Founder
- Saurav - Co-Founder & Co-lead
- Hamza - Core Developer & Team
- Abhishek - Support Team
- And Also Our Hardworking Maintainers
// Checkout the latest changes you get //
Latest Changelog: https://ppui.site/changelog
// A screenshot is worth of thousand words //
Latest Screenshots : https://ppui.site/gallery
NOTE : Well here you get all the useful features and with updating source every month it's hard to keep all the threads updated everytime everywhere so kindly visit our website for latest changes and screenshots.
--------- Official Download Server ! ---------
Note: You can check our Website for more details, guides , changelog etc related to build !
-- DEVICE UPDATE TELEGRAM CHANNEL --
-- SUPPORT/DISCUSSION TELEGRAM GROUP --
-- Visit our OFFICIAL Website
-- OUR OFFICIAL TWITTER HANDLE --
NOTE: It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
CLEAN FLASH :
- Download the latest build
- Take a backup, using Swift Backup
- Reboot to recovery.
- Format Data
- Flash the latest build
- Flash Recovery LineageOS by Magicxavi
- Reboot to recovery
- Reboot
DIRTY FLASH :
- Download the latest build
- Take a backup, using Swift Backup
- Reboot to recovery
- Flash the latest build
- Flash Recovery LineageOS by Magicxavi
- Reboot to recovery
- Reboot
What works?
Wifi | RIL | Mobile data | GPS | Camera
Flashlight | Camcorder | Bluetooth | Fingerprint reader | Lights | Sound | vibration
Almost everything
What doesn't work?
Nothing yet
You tell me!
BUG REPORT !!
As soon as the problem occurs, take a logcat and please inform us via Telegram or XDA.
for more READ THIS
- Android Open-Source Project
- Pixel Experience
- LineageOS
- Proton-AOSP
- AOSPA
- Others, I forgot to mention
PixelPlusUI XDA Templates credit goes to
- GOUSAL TONI
- Android OS version: 12.1
- Security patch: August 2022
- Build author/Device Maintainer : <VitorSSSouzaBR>
- DEVICE: <Xiaomi Mi A3>
- DEVICE CODENAME: <laurel_sprout>
Sources and Documentation
- ROM Source Code
- Kernel Source
- OFFICIAL DEVICES
// Giving little CAN HELP A LOT //
- As you know build is free but building ROM needs a server. And Maintaining source and device stuff needs a server and it's pretty expensive for a student.
- Do consider donating on Patreon for sustainable support and rewards or buying me a coffee if you want to appriciate our work.
- Thank you for your support !
​

I installed this ROM and currently only have one complaint. Vibration is off for Gboard, the virtual navigation buttons, the fingerprint scanner, and pattern unlock. This is regardless of what I set under Settings > Sound & Vibration.
Vibration is working fine for notifications and calls. It's just the haptics that aren't working for me.
incidentally, is there a Gcam version recommended for this ROM?

i've been using this rom for like 3 days and i love it !
it has all the features i'd expect from ppui.
one feature i kinda missed is disabling annoying notifications (meaning making all notifications silent while screen is on)
also can i use a custom kernel on top of this ?

Hello, does it work with android auto (phone call with car speaker, navigation and so on)?

Edited

The ROM works great! It's currently the best one for our phone.

[BUG]
Your rom does not work with AndroidAuto, i cannot answer/make call because when the call starts i cannot listen from the car, i can listen from the phone speaker, the menù on the car display says bluetooth but the phone use its own speaker.
The bluetooth remain connected in the phonr when i turn off the car, after several time the phone "think" that is connected to the car, and i cannot do calls, until i turn manually off the bluetooth.
Is there something to do/try?
Thanks

Rom is great. Only thing that is annoying 8s that usual random a12 bug where I can't here the other person on apps like Viber or whatsapp

Zergrinch said:
I installed this ROM and currently only have one complaint. Vibration is off for Gboard, the virtual navigation buttons, the fingerprint scanner, and pattern unlock. This is regardless of what I set under Settings > Sound & Vibration.
Vibration is working fine for notifications and calls. It's just the haptics that aren't working for me.
incidentally, is there a Gcam version recommended for this ROM?
Click to expand...
Click to collapse
For me it is working perfectly, I recommend you to join the device support group

mjdmjd86 said:
i've been using this rom for like 3 days and i love it !
it has all the features i'd expect from ppui.
one feature i kinda missed is disabling annoying notifications (meaning making all notifications silent while screen is on)
also can i use a custom kernel on top of this ?
Click to expand...
Click to collapse
Yes, but if there is a bug after installing a custom kernel, don't look for me to report bugs

lospo said:
Hello, does it work with android auto (phone call with car speaker, navigation and so on)?
Click to expand...
Click to collapse
I don't have a car so try and let me know

lospo said:
[BUG]
Your rom does not work with AndroidAuto, i cannot answer/make call because when the call starts i cannot listen from the car, i can listen from the phone speaker, the menù on the car display says bluetooth but the phone use its own speaker.
The bluetooth remain connected in the phonr when i turn off the car, after several time the phone "think" that is connected to the car, and i cannot do calls, until i turn manually off the bluetooth.
Is there something to do/try?
Thanks
Click to expand...
Click to collapse
I recommend joining the support group and sending the bug along with the log

sotmax said:
Rom is great. Only thing that is annoying 8s that usual random a12 bug where I can't here the other person on apps like Viber or whatsapp
Click to expand...
Click to collapse
I'm working on fixing it, it's a really annoying bug

VitorSSSouzaBR said:
I recommend joining the support group and sending the bug along with the log
Click to expand...
Click to collapse
Ok, i just send the log (MatLog with root privileges) and the bug to the gruoup.
Thank you so much!

VitorSSSouzaBR said:
I'm working on fixing it, it's a really annoying bug
Click to expand...
Click to collapse
To help you a little bit with app behaviour.
On Viber video call they can hear me but i can't. On normal Viber call all working ok. If I connect my earbuds all working ok even on video call. If I swap output from bt to speaker during call with Bluetooth, then speaker working great. On some previous builds I manage to just press speaker off and on and working.
To my knowledge vider and all other VoIP apps can't detect speaker at all unless you have one more source(bt, cable earpiece etc).
Also in volte calls I can't hear anything from earpiece at all. I have to disable volte if I want to have normal calls but this is a wide spread bug but is from system if has something to do. In general VoIP calls are misbehaving .
Hope that helps

Hi bro,
Really i love this rom a lot but i have something annoying me that the mic sensitivity is to high that make the sound on my ear too loud can i decrease it ?

guys if you facing internet calls problems try to disable this flag under developer options to see if it's fixed. I think this flag is causing the issue where you can't hear the other person and its for choosing audio output .
Give some feedback to see if it's ok for you as for me seems fixed now

There is a bug on locksreen clock, it freezes during the sleep.

Is this ROM still under development? For me it's the best one for our phone, only locksreen clock is the problem. If that can be fixed it would be perfect.

Hi,
This ROM is really awesome, really good Today is the 8th day I'm using this ROM, so far it's running smoothly, there are only a few problems with the camera and banking applications, but the camera can be tricked by using Parrot's GCam, but I haven't found the Bank application yet. Can you tell me how to use the Bank App, the bank app always closes automatically.
Thanks a lot

No more sound on my Asus Zenfone 5

My Asus Zenfone 5 is beginning to have some malfunctions :
No more sound, which means :
I can't make calls (the phone freezes to black and I can only start it up again by holding the power button)
I can't receive calls (callers go directly to voicemail)
I can't open the camera to take pictures or videos
Alarms don't ring, they just vibrate
I can't listen to music
I can't watch videos (videos taken with my phone, on youtube, on any social media app...) : video just won't start.
I got this bug report from NewPipe, a youtube client :
Exception​
User Action: play stream
Request: Player error[type=ERROR_CODE_AUDIO_TRACK_INIT_FAILED] occurred while playing
Content Country: GB
Content Language: en-
App Language: fr_FR
Service: YouTube
Version: 0.25.0
OS: Linux Android 9 - 28
Crash log
com.google.android.exoplayer2.ExoPlaybackException: MediaCodecAudioRenderer error, index=1, format=Format(null, null, null, audio/raw, null, -1, null, [-1, -1, -1.0], [2, 44100]), format_supported=YES
at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:566)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:198)
at android.os.HandlerThread.run(HandlerThread.java:65)
Caused by: com.google.android.exoplayer2.audio.AudioSink$InitializationException: AudioTrack init failed 0 Config(44100, 12, 44100)
at com.google.android.exoplayer2.audio.DefaultAudioSink$Configuration.buildAudioTrack(DefaultAudioSink.java:2110)
at com.google.android.exoplayer2.audio.DefaultAudioSink.buildAudioTrack(DefaultAudioSink.java:1070)
at com.google.android.exoplayer2.audio.DefaultAudioSink.buildAudioTrackWithRetry(DefaultAudioSink.java:1049)
at com.google.android.exoplayer2.audio.DefaultAudioSink.initializeAudioTrack(DefaultAudioSink.java:846)
at com.google.android.exoplayer2.audio.DefaultAudioSink.handleBuffer(DefaultAudioSink.java:929)
at com.google.android.exoplayer2.audio.MediaCodecAudioRenderer.processOutputBuffer(MediaCodecAudioRenderer.java:703)
at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.drainOutputBuffer(MediaCodecRenderer.java:1894)
at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.render(MediaCodecRenderer.java:792)
at com.google.android.exoplayer2.ExoPlayerImplInternal.doSomeWork(ExoPlayerImplInternal.java:989)
at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:490)
... 3 more
Suppressed: com.google.android.exoplayer2.audio.AudioSink$InitializationException: AudioTrack init failed 0 Config(44100, 12, 44100)
... 13 more
I don't know if it's related, but I've also noticed that in the play store, when I check the the compatibility of any app with my device, it is identified as Asus UNKNOWN_PRJ_ID, instead of X00QD.
I don't know how to proceed from there, is my phone fixable ?
The last time it happened, I was able to fix the issue by shutting down and restarting the phone a dozen times, but this time it's not working.

Llorenzaccio said:
My Asus Zenfone 5 is beginning to have some malfunctions :
No more sound, which means :
I can't make calls (the phone freezes to black and I can only start it up again by holding the power button)
I can't receive calls (callers go directly to voicemail)
I can't open the camera to take pictures or videos
Alarms don't ring, they just vibrate
I can't listen to music
I can't watch videos (videos taken with my phone, on youtube, on any social media app...) : video just won't start.
I got this bug report from NewPipe, a youtube client :
Exception​
User Action: play stream
Request: Player error[type=ERROR_CODE_AUDIO_TRACK_INIT_FAILED] occurred while playing
Content Country: GB
Content Language: en-
App Language: fr_FR
Service: YouTube
Version: 0.25.0
OS: Linux Android 9 - 28
Crash log
com.google.android.exoplayer2.ExoPlaybackException: MediaCodecAudioRenderer error, index=1, format=Format(null, null, null, audio/raw, null, -1, null, [-1, -1, -1.0], [2, 44100]), format_supported=YES
at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:566)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:198)
at android.os.HandlerThread.run(HandlerThread.java:65)
Caused by: com.google.android.exoplayer2.audio.AudioSink$InitializationException: AudioTrack init failed 0 Config(44100, 12, 44100)
at com.google.android.exoplayer2.audio.DefaultAudioSink$Configuration.buildAudioTrack(DefaultAudioSink.java:2110)
at com.google.android.exoplayer2.audio.DefaultAudioSink.buildAudioTrack(DefaultAudioSink.java:1070)
at com.google.android.exoplayer2.audio.DefaultAudioSink.buildAudioTrackWithRetry(DefaultAudioSink.java:1049)
at com.google.android.exoplayer2.audio.DefaultAudioSink.initializeAudioTrack(DefaultAudioSink.java:846)
at com.google.android.exoplayer2.audio.DefaultAudioSink.handleBuffer(DefaultAudioSink.java:929)
at com.google.android.exoplayer2.audio.MediaCodecAudioRenderer.processOutputBuffer(MediaCodecAudioRenderer.java:703)
at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.drainOutputBuffer(MediaCodecRenderer.java:1894)
at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.render(MediaCodecRenderer.java:792)
at com.google.android.exoplayer2.ExoPlayerImplInternal.doSomeWork(ExoPlayerImplInternal.java:989)
at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:490)
... 3 more
Suppressed: com.google.android.exoplayer2.audio.AudioSink$InitializationException: AudioTrack init failed 0 Config(44100, 12, 44100)
... 13 more
I don't know if it's related, but I've also noticed that in the play store, when I check the the compatibility of any app with my device, it is identified as Asus UNKNOWN_PRJ_ID, instead of X00QD.
I don't know how to proceed from there, is my phone fixable ?
The last time it happened, I was able to fix the issue by shutting down and restarting the phone a dozen times, but this time it's not working.
Click to expand...
Click to collapse
Stating the obvious, it could be hardware related. Has the phone been dropped ever or been contact by liquid, water, etc?
Are you running stock ASUS ROM?
You could back up and try factory reset.