Constantly stuttering audio. All Android-x86 versions since 4.4 RC1.

[Ícaro Albuquerque]

Hi guys, the title of the thread already says what's going on, but let me explain it better. The audio begins to stutter in three situations:

1. right when I unlock my PC

2. when Google's hotword (aka Ok Google) recognition service runs

3. if I leave my PC on and idle for too long

Logcat shows something related do sleep_time in audio_hw_primary (probably libasound.so) and also some errors related to PCM read/write. Can any of you please help me with this?

It has happened in all Android-x86 4.4 versions and it still plagues me in r1.

My audio chipset is a Conexant Cx20584 if that's of any use.

[Ícaro Albuquerque]

Little correction here: it's "related to", not "related do". Sorry.

So, has it really got to do with libasound or is it something else? Maybe incompatible hardware? I appreciate any help.

[CJLiqueira Belém - Pará - Brazil]

Dear Icaro! You did not say if "before" installing the Andriod, PC was emitting "AUDIO" mayor! Not said is allocated in partition in Hard disk Dual-boot! 

II created a USB-boot for Android 4.4 RC2, which was created by the program in Windows, the name "LinuxLive USB Creator" installation is only you indicate the ROM of Android, it incorporates the Boot. And I did so and the Android version! Perfectly recognized the audio by simple native program instalção 4.4 RC2!

Just for your information, I will describe DATA from my machine when I installed WindowsXP, with all audio configuration. I know it has nothing to do with your machine. Just what it was before the installation of ANDROID. Proveitar go to your question and if "open" Android, I installed and gave "BUG" after I activated the Modem SimCard my this my notebook. Thought! If I binding the installation with my Google account, through recognized my phone number from my SamrtPhone. Would you have the service that Google Play stopped and this version was straight and then displaying the messages: "Google Play Services stopped." And "The com.google.process.gapps process stopped." In small and accumulative windows. So I'm going today to the project Tieto-Multiwindow Android, the members here of the "Google Group" are sending direct.

Status do "Audio" no WINXP antes da instalação do Android 4.4 RC2 de 20052014 - FUNCIONANDO PEFEITO

*** Dispositivos comuns ***

Nome do sistema: ........Positivo Mobile 

Nome do processador: ....Intel(R) Core(TM)2 Duo CPU T6500 @ 2.10GHz 

Nome da BIOS: ...........BIOS Revision: 1.00.13POL 

Nome da placa de vídeo: .SiS Mirage 3 Graphics 

Memória instalada: ......4,00 GB 

*** Dispositivos de áudio ***

Realtek High Definition Audio: HDAUDIO\FUNC_01&VEN_10EC&DEV_0662&SUBSYS_15580801&REV_1001\4&1D070E81&0&0001 - Realtek

*** Programas instalados ***

Realtek High Definition Audio Driver: Realtek Semiconductor Corp. 5.10.0.5672

*** Módulos carregados ***

audiosrv.dll: c:\windows\system32\audiosrv.dll - 5.1.2600.5512 (xpsp.080413-0845)

*** Irqs ***

18: Driver de Barramento Microsoft UAA para High Definition Audio

*** Memória ***

0xD8400000-0xD8403FFF: Driver de Barramento Microsoft UAA para High Definition Audio

*** Drivers ***

Microsoft Kernel DRM Audio Descrambler: C:\WINDOWS\system32\drivers\drmkaud.sys - Parado                                                      

Driver de Barramento Microsoft UAA para High Definition Audio: C:\WINDOWS\system32\DRIVERS\HDAudBus.sys - Em execução                                                 

Service for Realtek HD Audio (WDM): C:\WINDOWS\system32\drivers\RtkHDAud.sys - Em execução       

Microsoft Kernel Wave Audio Mixer:  C:\WINDOWS\system32\drivers\kmixer.sys - Em execução                                                 

Microsoft Kernel Audio Splitter: C:\WINDOWS\system32\drivers\splitter.sys                          Parado                             

Microsoft Kernel System Audio Device: C:\WINDOWS\system32\drivers\sysaudio.sys - Em execução

Microsoft WINMM WDM Audio Compatibility Driver: C:\WINDOWS\system32\drivers\wdmaud.sys - Em execução

Em domingo, 31 de agosto de 2014 02h30min15s UTC-3, Ícaro Albuquerque escreveu:

Little correction here: it's "related to", not "related do". Sorry.

So, has it really got to do with libasound or is it something else? Maybe incompatible hardware? I appreciate any help.