yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] electrikjesus:
UPDATE: 02.04.17 - bliss-x86_64_n7.1.1r13_02.03.17_k4.10rc6-dev_03.iso

I have uploaded a new Unstable build to AFH. I remembered to merge all the sound fixes too this time. I had quite a few goes at adding the IPTS support for some touchscreens, but every patch or commit I found needed too many changes to other things in order to support it. So I opted to use a different method that used a few things in the firmware for the kernel to use at runtime on these devices. hopefully it works. Remote desktop on Bliss-x86 should be working in this build, I also did a little work to networking, sleep/power handling, CPU throttling for many devices, and a few more m sure. As far as not working, Gmail app is still giving me issues. That's about it.

Enjoy!!
[BLISS ROMS Development] electrikjesus:
Here's a quick walkthrough of how I edit my UEFI boot entry from Bliss-x86:

[youtube]dRpnPmMFgJE[/youtube]
[BLISS ROMS Development] grayhaze:
Still no luck with the touchscreen on the SP4 unfortunately, and this build randomly reboots on that device. It's possible that you might have more luck with https://github.com/ipts-linux-org/ipts-linux on the 4.1 kernel, as after more reading it looks like the ipts-linux-new repo is based on the 4.9 kernel and the previous one was based on 4.1. I believe there's more required than just the patches in that repo though, as some driver files from the SP4 Windows installation are required to be copied over and symlinked. I suspect with Android these would need to be baked into the build rather than copied over post-install. There's a bit more information on this over on Reddit: https://www.reddit.com/r/SurfaceLinux/comments/4vbzki/androidx86_with_the_new_ipts_driver/

Thanks again for all the work you've put into trying to get this work for us SP4 owners. It's much appreciated.
[BLISS ROMS Development] electrikjesus:
Man, why does M$ gotta be all difficult like that. The earliest kernel I can build with 7.1.x is 4.4, and it looks like the changes made would result in a kernel that would screw over every i915 chipset... That's not an idea solution for the masses. I will work at building a kernel for it in my free time, but I don't want to build your hopes up too high just yet.
[BLISS ROMS Development] lollyjay:
[MENTION=928479]electrikjesus[/MENTION] I know that you are concentrating on other devices. I just want to say that your bliss-x86_64_n7.1.1_01.11.17_r12_02_ej.iso build is working for 23 students on Lenovo ThinkPad Twist 3347 units that were destined for bulk disposal. They are now in daily use in one of our school's science classrooms and dual boot along with Win10. Thanks again for your work. Only minor bug is not automatically connecting to WiFi after booting Bliss.
[BLISS ROMS Development] wally86:
Dell Venue 11 Pro 7140 Core M with Bliss x86 n7.1.1

Hello everyone,

After trying many different version of Android x86, Remix OS, and Bliss x86, I was looking for some help. On Bliss x86 7.1.1 lastest stable i got working...

Bliss x86 n7.1.1_01.11.17_01_r12_02 Stable

Touchscreen Screen = Works

Audio = Works

Volume and Power Buttons = Work

Wifi = Works

Slim keyboard with trackpad = All Works

Problem i got is bluetooth turns on, connects, and then after about 5 seconds disconnects, loops over and over. Intel 7265 AC wifi + Bluetooth 4.0 LE

Only x86 that bluetooth worked perfect in was Remix OS x86 newest version. Any ideas?

https://www.fosshub.com/Remix-OS.htm...2016112201.zip

Other thing was the only version of screen rotation that worked was CM-x86 13.0-rc1

https://osdn.net/frs/redir.php?m=pum...6-13.0-rc1.iso

If anyone could help in anyway to get those two things working that would be amazing. Thanks
[BLISS ROMS Development] electrikjesus:
The thing is, each and every one of those have a different kernel and/or firmware that they package with the release. Sometimes, like in our case with the Unstable builds, the updated kernel might have issues with older patches and such. We pulled all the firmware Nice and Android-x86 project both have and added it to this kernel, but there might be patches made to their kernel that we wouldn't have for certain devices.
[BLISS ROMS Development] electrikjesus:
UPDATE 02.09.17 - BLEEDING EDGE BUILDS - 32 & 64 BIT

I am in the process of uploading a new build for both 32 & 64 bit. Lots to look forward to on this build, CPU updates, GPU updates, power updates, Oh My!!

Hundreds of device updates

New Kernel-4.10rc7-blissified-android-x86

Fixes to issues with Play Store on 64 bit builds

Fixes for Sleep & Wake issues (Make sure you check second post for new grub layout)

Added support for quite a few chipsets to the kernel

Added screen recorder hotkey (VolUp+Power)

Bunches more, check out GitHub for details

Things are still not quite perfect on all machines, but it's more progress at least. :)

Edit: These "UNSTABLE" builds are being renamed to Bleeding Edge, cause that name is a better description of the builds.
[BLISS ROMS Development] rajnallan:
Hi, Really appreciate the enormous amount of work you are putting in. I also use surface pro 3. Does the auto orientation change work for you to switch to landscape/portrait mode? If so how did you do it? Thnaks
[BLISS ROMS Development] electrikjesus:
No, that is something I can't figure out just yet. Even the solutions for Linux need to use a third party app or script. At least for this device. There was a Python script I came across, but it wouldn't work without a ton of work. Over my head for now.

For now ;)
[BLISS ROMS Development] rajnallan:
Thanks for the response. Appreciate. I did not try third party apps. The surface pro 3 has the necessary sensor and I checked and it is working. That is why I asked you. Thanks
[BLISS ROMS Development] romulo85:
Hi there electrikjesus , thanks for your work :)

I reached you on twitter, in the hopes of helping you out with development. I am using a Surface 3 and the image I tested (on USB boot) was the 4.10RC6 which had Sound control (with the volume buttons, but no sound at all), Graphics, Touch (haven't tested multitouch), Wake/Sleep (at least the screen turned off), The Windows Logo button also worked. When I tested RC7, only Graphics and touched worked. Where I can download the sources to compile and do you have a compilation guide? Thanks for the amazing work, hopefully we can do it together :)
[BLISS ROMS Development] electrikjesus:
PM me on here or hit me up on Hangouts, and I would love to help you get going.
[BLISS ROMS Development] rajnallan:
Couple of questions:

1 what custom recovery is built-in

2 How do I boot to recovery? When I click on the boot option today on surface pro 3 with Bliss installed on HDD partition it totally reboots and not to recovery. The soft reboot option works well.

3 How to optimize to use Google duo on Bliss

4 How to enhance audio

5 Can we add Dolby Atmos

The above questions are related to Bliss installation on surface pro 3. I have to say that newest unstable build is actually quite stable so far. Thanks
[BLISS ROMS Development] electrikjesus:
1) no recovery really, it's the one that Android-x86 Project adapted for PC's. 2) You don't really, it just loads the bootloader as normal. 3) I have no clue how yet 4) Search for my post about adding A.R.I.S.E Sound system. 5) You could in theory use the Atmos add-ons for Arise
[BLISS ROMS Development] Yong73:
i have sp3 too. is it working better than remix is. on remix its almost perfect.

从我的 iPhone 发送，使用 Tapatalk Pro
[BLISS ROMS Development] rajnallan:
I agree completely. Only problem is that wifi connection is not stable. I have to switch off and switch on Airplane mode. Otherwise so far brilliant and a brilliant job by the developer. Kudos
[BLISS ROMS Development] JCUK89:
Hi, I'm on your latest bleeding edge x64 build and have SP3. It's near perfect, only thing left is the unstable wi-fi. I'm not that fussed about the rotation. Thanks for your hard work.
[BLISS ROMS Development] electrikjesus:
We have a Bliss-x86 specific Telegram group now!!! http://telegram.me/blissx86
[BLISS ROMS Development] Yong73:
wifi is the most important thing, if it will be fixed, I will immediately switch from remix os to this. thanks.
[BLISS ROMS Development] electrikjesus:
Oh yeah, forgot to mention this one. It's a known issue, but only on a small number of test devices, none of which I own, so I couldn't troubleshoot
[BLISS ROMS Development] TheXorg:
Concerning the UEFI installer.. as you got the source code on GitHub, you could use their "Releases" to host the exe files
[BLISS ROMS Development] digital0:
I managed to start boot 8.0 from UEFI grub, but I get lots of messages "Failed to alloc mem for rom" and then it reboots. Any idea howto fix it?
[BLISS ROMS Development] tobad:
could using the system.sfs instead of system.img cause this problem (read/write problem)?

because in your 8.0-alpha.iso there is no system.img inside the system.sfs.

so i use the system.sfs with

menuentry 'Bliss-x86 8.0-Alpha' --class android {
search --file --no-floppy --set=root /BlissOS/system.sfs
linux /BlissOS/kernel root=/dev/ram0 androidboot.selinux=permissive quiet DATA=/BlissOS
initrd /BlissOS/initrd.img
}
[BLISS ROMS Development] electrikjesus:
No, this issue is something with Telcomm or phone app. It doesn't happen on any of my devices, but one of my testers with a yoga book, it happens to them.
[BLISS ROMS Development] electrikjesus:
change "DATA=/BlissOS" to "DATA=" for starters, that bit has changed

Maybe add "SRC=/BlissOS"
[BLISS ROMS Development] tobad:
awesome!!! that was the secret. you should propably update your installation instruction with that info :)

with "DATA=" the com.android.phone error is not coming up. google services stopps sometimes but I can complete the setupwizard.

with "SRC=/BlissOS-8.0-Alpha" booting takes just seconds. without this parameter booting takes 5 minutes!

EDIT: booting takes sometimes 1 minute but mostly 5-10 minutes. strange

here my multiboot setup

menuentry 'Bliss-x86 7.2 k4.4' --class bliss {
search --file --no-floppy --set=root /BlissOS-7.2_k4.4/system.img
linux /BlissOS-7.2_k4.4/kernel root=/dev/ram0 androidboot.selinux=permissive quiet DATA=/BlissOS-7.2_k4.4
initrd /BlissOS-7.2_k4.4/initrd.img
}

menuentry 'Bliss-x86 7.2 k4.9' --class bliss {
search --file --no-floppy --set=root /BlissOS-7.2_k4.9/system.img
linux /BlissOS-7.2_k4.9/kernel root=/dev/ram0 androidboot.selinux=permissive quiet DATA=/BlissOS-7.2_k4.9
initrd /BlissOS-7.2_k4.9/initrd.img
}

menuentry 'Bliss-x86 8.0 Alpha DATA + SRC ' --class bliss {
search --file --no-floppy --set=root /BlissOS-8.0-Alpha/system.sfs
linux /BlissOS-8.0-Alpha/kernel root=/dev/ram0 androidboot.selinux=permissive quiet SRC=/BlissOS-8.0-Alpha DATA=
initrd /BlissOS-8.0-Alpha/initrd.img
}

you think there will be an app compatible bridge (running nativ arm libs) in android 8?
[BLISS ROMS Development] electrikjesus:
Awesome!! I've updated the Windows UEFI installer with that info then and will run off a test build of the exe soon

Also, native bridge is fixed, I think... Logs show Houdini as running
[BLISS ROMS Development] fastguy:
Hi [MENTION=928479]electrikjesus[/MENTION], would you know how to enable extended desktop in Oreo? I searches everywhere in Google and this is a listed feature (multi-display) but there's no "how to" document to enable it.
[BLISS ROMS Development] electrikjesus:
I have an idea, but will need to get to that point. Right now, I'm in the middle of broadcasting the bringup for Bliss-x86 v8.1!!!

http://www.twitch.tv/electrikjesus0 if anyone wants to watch, and maybe learn something ;)
[BLISS ROMS Development] digital0:
Could you please add the attached file to /lib/firmware/brcm ? Then wifi works on my Onda obook 20 plus tablet.
[BLISS ROMS Development] electrikjesus:
I'll try to remember later, otherwise, feel free to make a pull request via our GitHub.

Push it here: https://github.com/BlissRoms-x86/device_generic_firmware/tree/dev-kernel.org/brcm
[BLISS ROMS Development] digital0:
Unfortunately something does not work. I did a fork, cloned locally my repo:

$ git clone git@github.com:nerijus/device_generic_firmware.git

$ git checkout origin/dev-kernel.org

$ git branch

* (HEAD detached from origin/dev-kernel.org)

mm6.0

$ git add brcmfmac43430a0-sdio.txt

$ git commit -a -m "add firmware txt"

$ git push origin origin/dev-kernel.org

But the new file did not appear in github. So I uploaded the file manually via github web and created a PR, but I would like to know how to do it normally in the future.
[BLISS ROMS Development] doddos920:
if you do not mind, please add EXE installer too, it's easier to install to Computer than using ISO files. Thanks.
[BLISS ROMS Development] tobad:
cat /sys/class/dmi/id/uevent

MODALIAS=dmi:bvnAmericanMegatrendsInc.:bvrT101HA.304:bd06/05/2017:svnASUSTeKCOMPUTERINC.:pnT101HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT101HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct32:cvr1.0:

couln'd identify in wich case statement i have to put the flags. can u help me again, and which flags do i have to set?

hal_sensors=true

or

has_sensors=true

what is the easiest way to modify init.sh? i tried modifying init.sh local through terminal but it says its a read-only filesystem. i tried then to gain read+write access but no success. any suggesstion??

my current workarround i copy system.img to usb and modifiy it on different pc in ubuntu using the following lines and copy it back to the Asus T101HA.

sudo mkdir /tmp/sysimg
sudo mount -t ext4 -o loop,rw system.img /tmp/sysimg
sudo nano /tmp/sysimg/etc/init.sh
sudo umount /tmp/sysimg
[BLISS ROMS Development] youling257:
*T101HA*)

hal_sensors=true

;;

8.0 or 7.1 ? 8.0 no system.img，only system.sfs，you need mksquashfs and unsquashfs.
[BLISS ROMS Development] tobad:
thanks i will try that.

r/w system problem: i'm using 7.1 with system.img (7zip extracted from system.sfs)

with the original "android-x86 7.1.2" the installer asks if i want read write access to system directory. i think it modifys the system.img, how can i do this manually?

EDIT: i found the problem. if i want to use the system.img i have to delete the system.sfs. looks like system.sfs has priority no mather what grub parameter has set! (/BlissOS-7.2_k4.9/system.img)

menuentry 'Bliss-x86 7.2 k4.9 modable' --class bliss {
search --file --no-floppy --set=root /BlissOS-7.2_k4.9/system.img
linux /BlissOS-7.2_k4.9/kernel root=/dev/ram0 androidboot.selinux=permissive quiet DATA=/BlissOS-7.2_k4.9
initrd /BlissOS-7.2_k4.9/initrd.img
}

here is some code of the original "android-x86 7.1.2" the installer script:

dialog --title " Question " --defaultno --yesno \
"\nDo you want to install /system directory as read-write?\n\nMaking /system be read-write is easier for debugging, but it needs more disk space and longer installation time." 10 61
instal_rw=$?

files="mnt/$SRC/kernel mnt/$SRC/initrd.img mnt/$SRC/$RAMDISK"
if [ $instal_rw -eq 0 ]; then
if [ "$fs" = "vfat" -o "$fs" = "fuseblk" ]; then
[ -e /sfs/system.img ] && sysimg="/sfs/system.img" || sysimg="mnt/$SRC/system.*"
else
sysimg="android/system"
fi
else
sysimg="mnt/$SRC/system.*"
fi
files="$files $sysimg"
size=0
for s in `du -sk $files | awk '{print $1}'`; do
size=$(($size+$s))
done
try_upgrade hd/$asrc
mkdir -p hd/$asrc
cd hd/$asrc
rm -rf system*
( ( cd /; find $files | $CPIO -H newc -o ) | pv -ns ${size}k | ( $CPIO -iud > /dev/null; echo $? > /tmp/result )) 2>&1 \
| progress_bar "Installing Android-x86" "Expect to write $size KB..."
result=$((`cat /tmp/result`*255))

if [ $result -eq 0 ]; then
for d in android mnt sfs ./$SRC; do
[ -d $d ] && mv $d/* . && rmdir $d
done
chown 0.0 *
for f in *; do
[ -d $f ] || chmod 644 $f
done

case "$fs" in
vfat|fuseblk)
[ -e data.img ] && check_data_img || create_data_img
;;
*)
mkdir -p data
;;
esac
fi

dialog --infobox "\n Syncing to disk..." 5 27
sync

return $result
[BLISS ROMS Development] jimgsey:
Need in root directory

Hello [MENTION=928479]electrikjesus[/MENTION]

I am a great follower of your work on the android-x86 platform for pc. I carry all your versions of the Blissrom on my desktop and my laptop. But recently I bought a tablet with UEFI that has a small problem :

I can not boot grub because of the bios. It's a Teclast X3 PLus. So to find this type of isos including linux, I need to run rEFInd as you know well.

I need all the files on android.86 to be able to get into the root of the partition without folders, so the system can start me. Data, kernel, system, initrd, ramdisk and install, all the programs in the root of the partition.

It is the only solution to be able to make it work. I already do with other distributions of android-86 but with your blissrom on this tablet I can not because I need a directory.

Could you help me? I just need those files to be able to run without needing them to be in a subfolder.

Thank you very much for reading and I await your response.
[BLISS ROMS Development] electrikjesus:
Have you tried the Oreo alpha? The installer for that is mostly inline with Android-x86's
[BLISS ROMS Development] jimgsey:
Hello,

I tried to extract Oreo x86, but I did not know there was a new installer for windows. Can you put the link to download it? please.

Thank you very much for responding so quickly!
[BLISS ROMS Development] electrikjesus:
I think you misunderstood me. The bootable installer from the iso...
[BLISS ROMS Development] franzli:
Hi, for me booting with grub works quite OK on uefi machines. Could of course be that refind is somehow more comfortable, haven't come around to trying yet, but just to let you know that if booting doesn't work, it's probably some other problem. (maybe you need to switch off secure boot?)
[BLISS ROMS Development] tobad:
i managed to change init.sh. but the screen doesnt rotate. still portrait mode. the grub menu is also in portrait.

is it possible to force orientation to landscape?
[BLISS ROMS Development] youling257:
the grub menu，why you want in landscape？it is impossible

the root@x8_64 in portrait，the Android bootanimation in portrait，it is impossible force landscape.

your tablet bios in portrait ?

my tablet bios in landscape，grub menu、root@x86_64、Android bootanimation，in landscape.

Android home、Android app，can force portrait.

in Android home，or open any one Android app，it can force landscape for you.

https://play.google.com/store/apps/details?id=nl.fameit.rotate

begin，i reply this，https://xdaforums.com/showpost.php?p=74831757&postcount=1161

https://xdaforums.com/showpost.php?p=74830379&postcount=1159
[BLISS ROMS Development] tobad:
my tablet bios in landscape

Gub menu in portrait

root@x86_64 in portrait

Android bootanimation in portrait

Android home、Android app，in portrait. <-------- switch To Landscape possible??

I'll try nl.fameit.rotate
[BLISS ROMS Development] kypor:
I also tried this with my Transformer Mini 102HA. It didn't work, but I think that is because there are no actual drivers for the system to use. :(
[BLISS ROMS Development] tobad:
with that ultimate rotation app i can rotate. do i have to use this 3rd party software or can i do it with built in settings?

now that i have a workong screen i detect the missing sound. its not possible to enable sound easily, right?

greetings
[BLISS ROMS Development] youling257:
so easy ! my 4.9 kernel include this patch，this patch from upstream.

cwhuang 7.1 rc2 4.9 kernel，no the patch. BlissOS-7.2_k4.9，of course missed many patches.

if you use 4.14 kernel，as you see，needn't any more patches for BYT/CHT.

T100HA、T101HA、T102HA，similar？ same acpi id？

From 3e8eb9d29d1c9364498fc78b4a31de05ba856a69 Mon Sep 17 00:00:00 2001

From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>

Date: Thu, 26 Jan 2017 14:09:37 -0600

Subject: [PATCH 435/656] ASoc: rt5645: add ACPI ID 10EC3270

ALC3270 is a low-cost version of RT5645, add ACPI ID

to enable probe and use rt5645 codec driver

Tested on Asus T100HA

Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>

Signed-off-by: Mark Brown <broonie@kernel.org>

Signed-off-by: youling257 <youling257@gmail.com>

---

sound/soc/codecs/rt5645.c | 1 +

1 file changed, 1 insertion(+)

diff --git a/sound/soc/codecs/rt5645.c b/sound/soc/codecs/rt5645.c

index 17317c9a3650..65ac8414a79b 100644

--- a/sound/soc/codecs/rt5645.c

+++ b/sound/soc/codecs/rt5645.c

@@ -3548,6 +3548,7 @@ static const struct acpi_device_id rt5645_acpi_match[] = {

{ "10EC5648", 0 },

{ "10EC5650", 0 },

{ "10EC5640", 0 },

+	{ "10EC3270", 0 },

{},

};

MODULE_DEVICE_TABLE(acpi, rt5645_acpi_match);

--

2.14.3
[BLISS ROMS Development] electrikjesus:
Hey Youling, do you have any ideas what is preventing Kernel-4.14.x to boot on 8.1? The only way I've been able to boot with that kernel is by using nomodeset.
[BLISS ROMS Development] youling257:
seem it is oreo-x86 problem，not the kernel problem.

you can use 4.14 kernel and modules to boot 7.1，first copy 4.14 modules to 7.1 system/lib/modules，then use 4.14 kernel to boot 7.1

sorry，i think of you electrikjesus as him tobad，i think tobad have to “nomodeset” boot 8.1

may be i was too tried last nightly.

cwhuang no time with 8.1，he prepare for OS2ATC 2017
[BLISS ROMS Development] bfmetcalf:
For a USB install. How do I create the data.img without RMX tools (no access to windows, only Linux).
[BLISS ROMS Development] electrikjesus:
The bootable usb installer will prompt for this if you choose NTFS or FAT32 install ;)

We also have this test version of a Windows Installer for Bliss OS

https://github.com/BlissRoms-x86/An...ob/master/bin/Androidx86-Installv256.0002.exe
[BLISS ROMS Development] bfmetcalf:
I think you misunderstood. I can't use the windows installer because, no windows. I think I figured out where my understanding broke down, I'm good to go now
[BLISS ROMS Development] tobad:
i booted 7.1 rc2 but no sound :/

how can i find out the acpi id of my T101HA soundcard?

greetings
[BLISS ROMS Development] youling257:
use any one kernel and modules to boot 7.1 rc2，ok? did yo understand it ?

---------- Post added at 10:42 AM ---------- Previous post was at 10:34 AM ----------

busybox mount Bliss-8.0.iso /data/1

busybox mount 7.1-rc2.iso /data/2

busybox mount /data/1/system.sfs /data/3

busybox mount /data/2/system.sfs /data/4

busybox cp -f -a /data/4/system.img /data/5

busybox mount /data/5/system.img /data/6

rm -rf /data/6/lib/modules/.

busybox cp -f -a /data/3/lib/modules/. /data/6/lib/modules

umount /data/6

busybox mount /dev/block/sda1 /data/7

busybox cp -f -a /data/6/system.img /data/7

busybox cp -f -a /data/1/kernel /data/7

busybox cp -f -a /data/2/initrd.img /data/7

busybox cp -f -a /data/2/ramdisk.img /data/7

busybox cp -f -a /data/2/boot/ /data/7

busybox cp -f -a /data/2/efi/ /data/7

---------- Post added at 11:00 AM ---------- Previous post was at 10:42 AM ----------

i edited #1211
[BLISS ROMS Development] youling257:
acpi id，for example
[BLISS ROMS Development] tobad:
thanks for response.

i installed the original android-x86 7.1 rc2. sadly there is also no sound neither.

i will check up the acpi id in windows ?.

with that commands i can copy modules from blissos 8.0 alpha to android-x86 7.1 right? you think sound will work after that modification?
[BLISS ROMS Development] Duk83:
asus t103ha sound

Hi all

I have tested many build of bliss-x86 on my asus transformer mini t103ha but sound not working.

It's possible to find a solution?

Sound Hardware:

Conexant I2S Audio Codec - (ACPI\14F10720)

Intel SST Audio Device (WDM) - (ACPI\808622A8)

Sorry for my bad English, i'm Italian
[BLISS ROMS Development] tobad:
did you try

* android-x86 7.1 rc2

* blissos 8.0 alpha

* phoenix os
[BLISS ROMS Development] Duk83:
I've already tried them, but no audio
[BLISS ROMS Development] youling257:
https://bugzilla.kernel.org/show_bug.cgi?id=115531#c3

https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/log/?h=topic/soc-cx2072x

cx2072x still not merge to upstream/Linux-next

this branch https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/log/?h=topic/soc-cx2072x-4.13

https://github.com/youling257/android-4.9/commits/experimental/android-mainline-tracking