Found the sound fix for baytrail please apply

[adam dubuque]

Hi I found a thread were they have patched and fixed the sound issues with android x86.
Please apply to android .IMG for efi
Especially 4.4r3

Here is the github fix: https://github.com/burzumishi/linux-baytrail-flexx10/issues/7

Thank you

[adam dubuque]

On BayTrail, sst-acpi currently selects the 5th IRQ listed in the HID=80860F28 device in the DSDT. On some machines this is incorrect, and prevents the DSP from starting up.

[Povilas Staniulis]

Main development focus is currently on 6.0 and 7.0, I don't think anyone
is going to update kitkat.
You're free to apply this patch yourself though. All sources are available.

[youling 257]

https://github.com/maurossi/linux/issues/1 

[youling 257]

https://git.kernel.org/cgit/linux/kernel/git/broonie/sound.git/log/?h=topic/intel ，many patch atom 5640

在 2016年10月9日星期日 UTC+8下午9:56:47，youling 257写道：

https://github.com/maurossi/linux/issues/1 

[adam dubuque]

i really appriciate the help and I feel like I am getting closer to a solution to getting my sound to work but here is my issue realistically
I have a baytrail windows 10 pc 2 in 1 it is a 64 bit using a 32 bit uefi and I am using the extreme GTX Android X86 installer and the 4.4r3 android .img because it will only load the .img images and it is the most stable with the most things working: wifi,touchscreen,video,auto rotate, volume buttons. etc.
only things not working are power off freezes, no bluetooth no camera and last but worst of all no sound. I can live with everything except no sound although if I use usb headset i can even have sound.
My issue is I have no clue how to get the sound working. Can someone please give me a laymens guide on how to make it work so that I can not only fix it myself but laso help the hundreds of tech retarded people out there who need this so badly. I promise to use this thread and give credit where credit is due.

I am not sure if I make changes they will even stick using this installer. I have it on the C: drive if not I need to know what to do please

[Martin]

4.4r3 android .img because it will only load the .img images

 

You can create a bootable usb and install whatever android version you want. Eg. marshmallow.

Yeah, there's small risk, that installer can replace your windows bootloader, but if you have grub installed already - you'll only have to change few lines in grub.cfg later. 

If you have any questions - I'm here to help.

[youling 257]

thanks very much ，https://groups.google.com/group/android-x86/attach/19c170e2e6f639/rtk_hciattach.tar.gz?part=0.1&authuser=0 

https://groups.google.com/d/msg/android-x86/kPBpj3CoXW4/Ofbm4nDBGQAJ

在 2016年10月9日星期日 UTC+8下午10:03:48，youling 257写道：

thanks very much ，https://groups.google.com/group/android-x86/attach/d1ffc290d6d56/alsa_bytcr_andx86.zip?part=0.1&authuser=0&view=1 

https://groups.google.com/d/msg/android-x86/un74okmr30g/Vm0NKfwfDQAJ

[adam dubuque]

Thank you
I do have a question I have a UEFI machine and can only seem to get the .IMG files to work (no .ISO) From what I understand the 6.0rc2 has sound working.
Is there a way to get the .ISO to boot on my machine Rufus won't do uefi with it and unetbootin works but my PC won't find the USB...

[adam dubuque]

I got 6.0rc2 loaded and installed. I realized I had to use the 64bit ISO unfortunately I still had no sound, Bluetooth, ect. And now videos are either not playing using YouTube app but YouTube through the browser they crash.

I am hoping to install 4.4r3 to an ext4 partition so I can move forward to a sound fix. For some reason I now can't get it to work using unetbootin either ISO or IMG. The way I did with 6.0

I really wish there was an apk or some kind of simple fix for this. I love this project and I love my PC I have been wanting dual boot for years and now I have it and for the life of me can't get audio unless I use a USB headset

[adam dubuque]

[adam dubuque]

My GOD!! Man why cant baytrail users get an android x86 for the thousands of baytrail devices out there with working sound???

cant you guys patch a kernel for us or make a distro please?? would rather a newer update but 4.4r3 seems to be the only one that everything works but sound unless you use some sort of usb soundcard which is a clumsy fix not even a fix at all.

Please I do not have a linux install to patch a kernel if I even knew how to. Im sure whoever does somehow come out with a laymens plug and play fix for the baytrail systems to have sound will be nothing short of a mega hero

PLEASE! HELP! US!!!

[Mauro Rossi]

Il giorno giovedì 3 novembre 2016 22:43:14 UTC+1, adam dubuque ha scritto:

My GOD!! Man why cant baytrail users get an android x86 for the thousands of baytrail devices out there with working sound???

cant you guys patch a kernel for us or make a distro please?? would rather a newer update but 4.4r3 seems to be the only one that everything works but sound unless you use some sort of usb soundcard which is a clumsy fix not even a fix at all.

Please I do not have a linux install to patch a kernel if I even knew how to. Im sure whoever does somehow come out with a laymens plug and play fix for the baytrail systems to have sound will be nothing short of a mega hero

PLEASE! HELP! US!!!

Hi,

 latest experimental kernel is here: https://github.com/maurossi/linux/tree/kernel-4.9rc3

Unfortunately even if I could build an iso image I could never successfully boot due to some permission (? or selinux issues ?)
and I don't think it would work with kitkat-x86

Maybe someone in the forum can interpret what is actually happening and provide clues for me to boot and for you to have a working iso image with sound drivers.
Mauro

[zefie altimitmine]

I had a build on my Nextbook that ran but the kernel was unstable and it would randomly reboot. You can try to hack at my existing builds to see if you can tweak them for your specific device. There was working sound on the Nextbook with some included scripts. Not sure how this build will react on a different model though. And I no longer have the nextbook to work on any baytrail projects anymore.

https://files.persona.cc/linux/intel_baytrail_soc/nextbook%2010.1/android/

Read the text files for each file. Also like I said you will probably have to modify some files in the system partition, namely the script that checks the model number.

Bluetooth never worked for me on the Nextbook, but I had everything else functional.

Good luck.

[youling 257]

how to make Brightness control work ? https://bugs.freedesktop.org/show_bug.cgi?id=96571 ，I don't think the latest pwm patch can work.

i don't know DSDT patch at all，the upstream sound patch needn't DSDT patch，the upstream sound patch for 4.8 kernel ，and 4.9 kernel merge it already . it should aif1 ssp0  for my tablet .

在 2016年11月4日星期五 UTC+8上午8:32:50，zefie altimitmine写道：

[youling 257]

the upstream base on https://github.com/plbossart/sound/tree/t100taf-7 ，but upstream didn't has “clk: x86: Add Atom PMC platform clocks” ，4.9 kernel don't has this patch yet https://patchwork.kernel.org/patch/9277989/

在 2016年11月4日星期五 UTC+8上午8:32:50，zefie altimitmine写道：

I had a build on my Nextbook that ran but the kernel was unstable and it would randomly reboot. You can try to hack at my existing builds to see if you can tweak them for your specific device. There was working sound on the Nextbook with some included scripts. Not sure how this build will react on a different model though. And I no longer have the nextbook to work on any baytrail projects anymore.

[youling 257]

battery staus

在 2016年11月4日星期五 UTC+8上午8:32:50，zefie altimitmine写道：

I had a build on my Nextbook that ran but the kernel was unstable and it would randomly reboot. You can try to hack at my existing builds to see if you can tweak them for your specific device. There was working sound on the Nextbook with some included scripts. Not sure how this build will react on a different model though. And I no longer have the nextbook to work on any baytrail projects anymore.

[adam dubuque]

Ill try it and report back thanks. anything i can do to help i will thank you guys

[zefie altimitmine]

I honestly forgot how I did most of what I did. And I don't have a baytrail to test with anymore which is why I'm not touching the existing code.

[adam dubuque]

I hate to say I tried it on my next book flexx 11 it started up and stayed in portrait mode, but the main thing was still no sound without a USB headset or speakers attached

--
You received this message because you are subscribed to a topic in the Google Groups "Android-x86" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/android-x86/hB0dlveMIRE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to android-x86+unsubscribe@googlegroups.com.
To post to this group, send email to andro...@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.

[adam dubuque]

What I dont understand is the manufactures put android on these exact machines exe the nextbook ares 11 with the same hardware and specs and it works fine and not just that machine tons of other baytrail hardware i dont understand why we cant get one of those images and engineer it to understand whats going on or for a fix. Is this a possability??

I notice the pipo w2 something or other has a dual boot system with almost the same hardware as mine but im to scared to flash the bios because i dont know enough to know if it will brick my machine

[youling 257]

test android_x86_010c.iso.xz ，get button work .

<6>[   29.777804] input: gpio-keys as /devices/platform/gpio-keys.0.auto/input/input5
<6>[   29.825852] input: gpio-keys as /devices/platform/gpio-keys.1.auto/input/input6

在 2016年11月4日星期五 UTC+8上午8:32:50，zefie altimitmine写道：

I had a build on my Nextbook that ran but the kernel was unstable and it would randomly reboot. You can try to hack at my existing builds to see if you can tweak them for your specific device. There was working sound on the Nextbook with some included scripts. Not sure how this build will react on a different model though. And I no longer have the nextbook to work on any baytrail projects anymore.

[youling 257]

my kernel，gpio-keys gpio-keys.1.auto: Unable to claim irq 8; error -16

49.119058] Baytrail Audio Port: ASoC: no backend DAIs enabled for Baytrail Audio Port 

61.959073] sst-mfld-platform sst-mfld-platform: Enter: enable=1 port_name=ssp0-port

Because at 61s，run /system/etc/init.sh，alsa_ctl -f $f restore $c ，so we can know boot time 12s .

在 2016年11月5日星期六 UTC+8下午3:34:54，youling 257写道：

[spin877]

[    8.973804] genirq: Flags mismatch irq 8. 00000083 (volume_down) vs. 00000080 (rtc0)
[    8.982493] gpio-keys gpio-keys.1.auto: Unable to claim irq 8; error -16
[    8.990315] gpio-keys: probe of gpio-keys.1.auto failed with error -16

for Resolving the problem above apply this patch
genirq: Flags mismatch irq 8. 00000080 (mmc0) vs. 00000000 (rtc0)
https://patchwork.kernel.org/patch/6118791/

[youling 257]

use DSDT patch can work，use this patch also work .

在 2016年11月7日星期一 UTC+8下午6:18:02，spin877写道：

[adam dubuque]

How do I use this or can you please put it in an ISO complete build for us to try it please??

[Milan Parikh]

Hey, you were the one who created the experimental build for the Surface 3, right? Thank you for that, it works wonderfully (except for sound, obviously).

[youling 257]

how to make backlight work on surface 3 ？ 6.0 rc2 experimental for surface 3，backlight can work ? https://bugs.freedesktop.org/show_bug.cgi?id=96571 ，drm:pwm_setup_backlight [i915]] *ERROR* Failed to own the pwm chip ，same problem .

在 2016年11月7日星期一 UTC+8下午11:17:48，Milan Parikh写道：

[adam dubuque]

I got 6.0 to run again no sound but the issue is it freezes and 4.4 doesn't look up. Seems to me that 4.4 KitKat is the most stable android build.

[spin877]

Also on my tablet I was + a year without audio.

these days I decided to try to recompile a kernel adroid-x86

I preferred the last 4.8 

and now it seems to work

the kernel and here

First race and replace the default fimware /lib/firmware/intel/fw_sst_0f28.bin with fw_sst_0f28_ssp0.bin (the network is also another grim fw_sst_0f28_ssp2.bin  )

and rename in fw_sst_0f28.bin

make changes in file sound/soc/intel/boards/bytcr_rt5640.c

line 765   "%s", "rt5640-aif1");// replace "rt5640-aif[1|2]"

line 777 "%s", "ssp2-port");// replace "ssp[0|2]-port"

create a structure to be inserted in byt_rt5640_quirk_table[]

in my case:

to carve vendor name and product name

use linux command :

dmidecode | grep -A3 '^System Information'

replace "Insyde" and "Baytrail" with your

another attempt should be made by replacing 

"BYT_RT5640_SSP2_AIF2|"  with 

BYT_RT5640_SSP0_AIF1 or 

BYT_RT5640_SSP0_AIF2

compile the kernel using config files Android-x86 arch/x86/configs/android-x86_defconfig

Once compiled the kernel and boot

run this script

if you use Android remember to rename each "amixer" in "alsa_amixer"

[youling 257]

if you know，the amixer script is half year ago by zefie altimitmine ，https://github.com/zefie/nxt_and_x86/tree/x86/files/6/system/etc/alsa

please you don't Misleading others about you edit line 765、777

the new progress is here，https://github.com/plbossart/sound/commits/intel/audio-latest-fixes ，ASoC: Intel: detect audio routing with CHAN package ，ASoC: Intel: bytct_rt5640: change default capture settings .

now needn't quirk bytcr_rt5640.c，

u0_a25@x86:/ $ su

root@x86:/ # dmesg | grep 5640

[    9.713293] bytcr_rt5640 bytcr_rt5640: BIOS Routing: AIF1 connected

[    9.738653] bytcr_rt5640 bytcr_rt5640: quirk IN1_MAP enabled

[    9.751237] bytcr_rt5640 bytcr_rt5640: quirk DIFF_MIC enabled

[    9.759567] bytcr_rt5640 bytcr_rt5640: quirk SSP0_AIF1 enabled

[    9.767415] bytcr_rt5640 bytcr_rt5640: quirk MCLK_EN enabled

[    9.797046] bytcr_rt5640 bytcr_rt5640: snd-soc-dummy-dai <-> media-cpu-dai mapping ok

[    9.821570] bytcr_rt5640 bytcr_rt5640: snd-soc-dummy-dai <-> deepbuffer-cpu-dai mapping ok

[    9.845684] bytcr_rt5640 bytcr_rt5640: rt5640-aif1 <-> ssp0-port mapping ok

root@x86:/ #

在 2016年11月9日星期三 UTC+8上午4:03:59，spin877写道：

[adam dubuque]

WOW!!! THIS LOOKS LIKE GRWAT NEWS!!! Thank you I hope it works out please let me know how I can help.

[spin877]

it is true, I Apologise, For Informations untrue. concerning code line 767 ,, 777.
it is not necessary
but it is also true that if you do not add this line, the audio on my tablet does not feel



        {
                .callback = byt_rt5640_quirk_cb,
                .matches = {
                        DMI_EXACT_MATCH(DMI_SYS_VENDOR, "Insyde"),
                        DMI_EXACT_MATCH(DMI_PRODUCT_NAME, "BayTrail"),
                },
                .driver_data = (unsigned long *)(BYT_RT5640_IN1_MAP |
                                                 BYT_RT5640_MCLK_EN),
        },
    


I ask again apologize. but I'm not a real programmer.

I think, that 80% of the BayTrail audio problems with rt5640 codec 
It is due to the fact that the firmware distributed with the kernel is not correct

[youling 257]

if you don't use HiFi file on Ubuntu or /system/etc/alsa/bytcrrt5640.state on Android x86，you don't say no sound . if only use amixer script can make sound，half year ago，i can make sound .

在 2016年11月10日星期四 UTC+8上午8:07:36，spin877写道：

[youling 257]

https://github.com/sfumato77/Kernel-4.8_Android-x86_BayTrail/commit/46060de20337fb0a931a56e02fb425d990c7ec27 ，seem you don't add this https://github.com/plbossart/sound/commit/2f797c8f7bda4312c305ac3733e0ee36482a0c9c ，

this patch，it will auto in1 map .

在 2016年11月10日星期四 UTC+8上午8:07:36，spin877写道：

it is true, I Apologise, For Informations untrue. concerning code line 767 ,, 777.
it is not necessary
but it is also true that if you do not add this line, the audio on my tablet does not feel

[Jose Luis s]

Really confusing for me.

So what's advised, Maurosi kernel 4.8 and plbossart sound patches or sfumato kernel 4.8?

is it necessary to use the bytcrrt5640.state file?

What about HiFi file?

Can anybody kindly offer some clear explanation of this options? It would be great for no so skilled members (like me).

Thanks all anyway for your work.

[youling 257]

https://github.com/plbossart/UCM/commits/master ，On 4.8 kernel Ubuntu，delete /var/lib/alsa/asound.state ，To enable UCM on RT5640 platforms,  copy directory to UCM location sudo cp -rf ../bytcr-rt5640 /usr/share/alsa/ucm ，reboot will get new /var/lib/alsa/asound.state ，copy /var/lib/alsa/asound.state to Android x86 /system/etc/alsa/bytcrrt5640.state . you can find my bytcrrt5640.state .

two years ago，/system/etc/alsa/bytrt5640.state ，it is 3.x、4.0.x Ubuntu /var/lib/alsa/asound.state . 

在 2016年11月11日星期五 UTC+8上午12:36:16，Jose Luis s写道：

[adam dubuque]

I have made progress...
Using these instructions I am now finding the baytrail soundcard and alsamixer is populating as it should. Problem is
A. There is still no sound and
B. After a restart it all goes away.
The blacklist remains and the files I added also remain but the command I make in debug modprobe snd-intel-sst-acpi
Goes away and must be done again. So I am assuming this is not occurring perminantly therefore it is only appearing to work.

Is there a way to make this write and stick so that it actually works and stays after a reboot???

Here is what I did, I got this from another poster on Google groups.

According to these:

http://mailman.alsa-project.org/pipermail/alsa-devel/2015-July/094429.html
http://mailman.alsa-project.org/pipermail/alsa-devel/2015-July/094664.html

fw_sst_0f28.bin and fw_sst_0f28_ssp0.bin (the latter renamed to fw_sst_0f28.bin) are used only when you use "snd-intel-sst-acpi" driver.

Your lsmod shows you are using "snd-soc-sst-acpi", so you are using the firmware file "fw_sst_0f28.bin-48kHz_i2s_master"

Suggest you use snd-intel-sst-acpi instead. One way to do so (note: Use the newest firmware files from previous post):

1) Blacklist snd-soc-sst-acpi on /system/etc/modules.blacklist (include these 2 lines - don't know if it is based on filename or internal driver name - won't husrt including both)

blacklist snd-soc-sst-acpi
blacklist snd_soc_sst_acpi

2) Boot under debug mode and before 2nd exit check which drivers are loaded with "lsmod". You shouldn't have snd-intel-sst-acpi on list.

3) Check if you have snd-intel-sst-acpi on the loaded driver list. If not, load it:

modprobe snd-intel-sst-acpi
OR
busybox modprobe snd-intel-sst-acpi

4) type dmesg and check you have any different info about your sound device (byt 5640). Check also if /proc/asound/cards exists and is not empty:

cat /proc/asound/cards

5) Continue booting and check if you have sound

6) If not, rename fw_sst_0f28_ssp0.bin to fw_sst_0f28.bin and repeat procedure from step 2.

[adam dubuque]

By the way I did this using 6.0r2
I am going to try it on 4.4r3 and report back

[adam dubuque]

[adam dubuque]

https://github.com/burzumishi/linux-baytrail-flexx10/issues/7#issuecomment-261927274

Now they are saying they have sound, headphones jack and mic working.

Can someone here help me reproduce this or create a working USB loader?

[adam dubuque]

It appears they got it all working using pulseaudio

[youling 257]

do you know no one than me know more about Android x86 sound ，if you can't understand my say，i haven't method . if you want iso for test，i haven't method .

they are make their tablet work well on Ubuntu，only me make my tablet work well on Android x86 . 

Android x86 isn't support HiFi，but support state，use state ，/system/etc/alsa/bytcrrt5640.state，needn't HiFi . 

on Ubuntu，setting sound use speaker and Internal Mic ，alsactl store bytcrrt5640 -f speaker，setting sound use headset and headset mic，alsactl store bytcrrt5640 -f headset ， copy speaker and headset two files to Android x86，alsa_ctl restore -f /sdcard/speaker ，alsa_ctl restore -f /sdcard/headset，Switching headphones and speakers on Android x86. /system/etc/alsa/bytcrrt5640.state is speaker or headset file .

[adam dubuque]

i'm using the .state file im getting alsa ctl not found when i enter your commands. I have tried everything you suggested.
that driver makes total sense perhaps you should try it and see if it works.

Also if you cant create a working iso how about a zip file i can put on an usb stick that i can install with?