[Q] CM12 - Audio Out issue with Skype (LogCat included) topic

I have been testing a couple CM11 builds on my Oneplus One and have run into the same issue with each one.

Audio output from the plugged in headset is dropping off at some point in a call. The only way to get it back is to unplug the headset and plug it back in, which only lasts for a short while.

Expected Result: When making a call with Skype using CM12 the outbound audio stream should not be interrupted.

Actual Results: After a short while the system seems to trigger an event that causes the outbound audio to shut down. The call remains connected but no audio from the device is sent via the microphone. Instead a surging sound is transmitted to the other end.

Steps

1. Plug in headphones with mic


2. Start Skype and make a call


3. Wait for the audio out to stop transmitting the microphone


4. Check logs for event

I am including the full logCat that I captured while testing. I am not sure if this is just a compatibility issue or some other known bug. Looking for answers has been fruitless.

Code:

---

01-05 11:50:01.607: D/ACDB-LOADER(247): ACDB -> AUDIO_SET_AUDPROC_VOL_CAL
01-05 11:50:01.607: D/ACDB-LOADER(247): ACDB -> send_afe_cal
01-05 11:50:01.607: D/ACDB-LOADER(247): ACDB -> ACDB_CMD_GET_AFE_COMMON_TABLE
01-05 11:50:01.607: D/ACDB-LOADER(247): ACDB -> AUDIO_SET_AFE_CAL
01-05 11:50:01.612: D/audio_hw_primary(247): select_devices: done
01-05 11:50:01.643: D/DownloadManager(4736): [6228] Starting
01-05 11:50:01.688: D/audio_hw_primary(247): in_standby: enter: stream (0xaf39e0c0) usecase(7: audio-record)
01-05 11:50:01.729: D/hardware_info(247): hw_info_append_hw_type : device_name = headset-mic
01-05 11:50:01.739: E/AudioFlinger(247): read failed: framesRead=-2147483631
01-05 11:50:01.739: D/audio_hw_primary(247): start_input_stream: enter: stream(0xaf39e0c0)usecase(7: audio-record)
01-05 11:50:01.739: D/audio_hw_primary(247): select_devices: out_snd_device(0: ) in_snd_device(47: headset-mic)
01-05 11:50:01.739: D/hardware_info(247): hw_info_append_hw_type : device_name = headset-mic
01-05 11:50:01.739: I/msm8974_platform(247): platform_send_audio_calibration: sending audio calibration for snd_device(47) acdb_id(8)
01-05 11:50:01.739: D/ACDB-LOADER(247): ACDB -> send_audio_cal, acdb_id = 8, path =  1
01-05 11:50:01.739: D/ACDB-LOADER(247): ACDB -> send_adm_topology
01-05 11:50:01.739: D/ACDB-LOADER(247): ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TOPOLOGY_ID
01-05 11:50:01.739: D/ACDB-LOADER(247): ACDB -> send_asm_topology
01-05 11:50:01.739: D/ACDB-LOADER(247): ACDB -> ACDB_CMD_GET_AUDPROC_STREAM_TOPOLOGY_ID
01-05 11:50:01.739: D/ACDB-LOADER(247): ACDB -> send_audtable
01-05 11:50:01.739: D/ACDB-LOADER(247): ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TABLE
01-05 11:50:01.739: D/ACDB-LOADER(247): ACDB -> AUDIO_SET_AUDPROC_CAL
01-05 11:50:01.739: D/ACDB-LOADER(247): ACDB -> send_audvoltable
01-05 11:50:01.739: D/ACDB-LOADER(247): ACDB -> ACDB_CMD_GET_AUDPROC_GAIN_DEP_STEP_TABLE
01-05 11:50:01.739: D/(247): Failed to fetch the lookup information of the device 00000008
01-05 11:50:01.739: E/ACDB-LOADER(247): Error: ACDB AudProc vol returned = -19

---

Current ROM install



Full LogCat during testing: http://pastebin.com/N0jKRFLp

Any idea of what is happening and how to fix?

Lg G3 Massive Battery Drain from bam_dmux_wakelock (Pics Included) topic

Alright everyone,

Some details about my phone before we begin-

I am a moderate user. I play some games, check emails, text and that's about it.

My phone is NOT rooted and obviously I am not running a custom rom, or a alternate launcher, and I haven't really modified many if at all any settings.

So, that being said I am experience some sever kernel wake lock issues form bam_dmux_wakelock for the past week or so. As you see in my picture, 6 out of my 7 hours of up time (off charger) has been kept from deep sleep, therefore destroying my battery time.

Today I have maybe 30-40 minutes total of screen on time, but not nearly the 6 hours of non deep sleep time.

I've turned off "okay google" detection, disabled wifi when screen is off, restricted background data for youtube, disabled google + (I don't use social media) and my brightness is on auto mode, typically around 35% when the screen is on.

If google can see this I would like to offer them a huge F you for changing the permission architecture so that gplay apps cant detected whats causing the wake-lock without root. They are pretty much forcing us to root our phones to access features locked meanwhile continuing to call android "Open Source"

Can anyone give me a recommendation on what are my options? Or should I really just root my phone, which I don't want to do (I have in the past but I haven't needed too with the G3 since it has everything I want without root)

Attached Thumbnails