yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] dedaol:
I have a Teclast X80H, Z3735F Atom, 2 GByte RAM, 32 GByte eMMC, RTL8723BS WLAN/BT chip. I could make BT work on it under linux, there were two things necessary:

- Adding the device ID in rfkill-gpio.c:

static const struct acpi_device_id rfkill_acpi_match[] = {
+ { "OBDA8723", RFKILL_TYPE_BLUETOOTH },
{ "BCM4752", RFKILL_TYPE_GPS },
{ "LNV4752", RFKILL_TYPE_GPS },
{ },

and making sure that the rfkill-gpio module is compiled (e.g. debian has RFKILL_GPIO as not set by default). The first character of the device id is a capital o, not a zero.

- Getting the rtl8723bs_bt driver from github, compiling it, installing it. It uploads the firmware necessary for BT to work. BT is actually running through a serial port, and one has to find out which one is the correct one by trying.
[BLISS ROMS Development] sintoo:
Why can't everyone be like the member I'mRonBurgandy?

Here is his reply one page before:

"The work around I did find is just using a Bluetooth dongle. The dongle seems to work fine."

His answer is specific to the question regarding a member's question about why Bluetooth. doesn't work.

As for you, my friend, clearly didn't understand the sentence: "if you don't have the answer to the specific question (simple way to increase the data to 3-4Gz), then the best for you to do is to not reply, to not waste your time to write and someone else's time to read". Now go back to beginning (1 page before) to see WHY I said that in the first place, and why I told him: only reply to any member's question if you know the answer. Just DON'T REPLY. Keep quiet. My friends, You're NOT required to answer if you don't know the solution to the INITIAL (I.N.I.T.I.A.L.) question. Good luck to you.
[BLISS ROMS Development] krono2:
las imagenes IMG no son boteables?
[BLISS ROMS Development] ElfinJNoty:
I am a Board Member of Team Bliss. Please respect me as such, and be respectful to all your fellow XDA members. [MENTION=928479]electrikjesus[/MENTION] and I as well as our other Team Members will be the ones to dictate how our threads will be run. Not you.

This is a support thread and we intend to do all we can to provide support. Negativity is neither encouraging towards continued development nor is it welcome here in this thread. You have made me regret replying to your initial post at all... Which may lead to less responses to other users who would find themselves grateful for our efforts. As well as the efforts of fellow XDA members who participate in the testing and discussion.

Install Bliss to your device's local storage or an SD card by following the flashing instructions in the original posts. You have the option of using a USB installer, or I recommend the easy Windows installer .exe.

If you are using a USB installer, you should be installing to an already made ext4 partition. Utilize the mentioned tools to resize or create a fresh data.img. Data is stored in an .img file, not as a separate partition.

It is now 7 days since your initial post so I have quoted two answers in addition to my reply today so that all relevant information is available together for you. You have either failed to read the clear answers to your initial inquiry or are choosing to be argumentative. In either case, I ask that this subject be put to rest and we can move on ?
[BLISS ROMS Development] franzli:
[MENTION=1857544]ElfinJNoty[/MENTION] you're absolutely right, but I guess in this case it may be best not to feed the troll.
[BLISS ROMS Development] kanttii:
New unofficial 64-bit build with kernel 4.9 and Mesa 17.1.5

Here: Bliss-v7.2-android_x86_64-UNOFFICIAL-20171007.iso

md5sum: 2a058d2b9089f83ff890a008d98a91f2

Extract the ZIP and flash to USB with Rufus on Windows or Etcher on Linux/Mac and follow the instructions in the first posts of the thread :)

64-bit Bliss-x86 with kernel 4.9 and Mesa 17.1.5 graphics drivers, plus:

Aptoide marketplace

F-Droid marketplace

DuckDuckGo search

extra Google apps like Chrome, Maps, Earth, Drive Suite, Pixel Launcher and more

Regular Bliss stuff like taskbar launcher and freeform windows

Nova Launcher (and its Google Now addon) for tablet use

preinstalled Pixel Nougat style icon pack (enable manually in Nova settings if you want to use it)

Firefox and Firefox Focus browsers

Where applicable, the app authors have given me permission to include these apps in PC build(s).

With the latest updates from @electrikjesus & Team Bliss, Android-x86 and others it's very smooth on my Surface Pro 3 so all thanks to them for fixing so much stuff!

There were issues creating a proper bootable ISO, so I had to first flash an old ISO to USB, then replace files, then create an image of the USB drive and after that shrink the image by checking actual sector count and creating a new image with dd using that sector count as the size pointer. It came out as a 2GB image.

4.13 & 4.14 didn't boot, it also didn't boot if I added in newer Nougat releases or graphics drivers so security patch is August 5th. Kernel does have newer patches, though. Gotta continue debugging.

3:25 AM, time to sleep :D
[BLISS ROMS Development] Guimenez:
Do you will compile 32 bits version?
[BLISS ROMS Development] cai_miao:
Can't use touchscreen on my Surface Book. Using Bleeding-edge IPTS build.
[BLISS ROMS Development] lucasdeeiroz:
downloaded it twice and for me it saying that this ISO is corrupted.
[BLISS ROMS Development] kanttii:
Did you try with https://etcher.io ? That works for me :)

Do you get the same md5sum from the downloaded ISO as in my post?

I will this week!
[BLISS ROMS Development] lucasdeeiroz:
I tried with Rufus, i was on Windows. I`ll try etcher today.
[BLISS ROMS Development] cai_miao:
According to blog-yoitsu-moe/arch-linux/get_surface_book_2.html ,

Surface Book should use 0076, but I find it hard to mount system as rw, and using Windows installer to locally install Bliss x86 (on NVMe) is not bootable, so I need help from devs.
[BLISS ROMS Development] kanttii:
Did it work?
[BLISS ROMS Development] cai_miao:
I insalled on an usb device, sticked into a linux workaround and modified soft links of respective files, results in touch screen not working. Help needed.
[BLISS ROMS Development] 4r44444:
I succesful boot this on my CHUWI HI12 Tablet!

-Wifi Works

-Keyboard works

- Display works

Not Works:

Sound

Touch

Is it possible to fix this or impossible without device sources?
[BLISS ROMS Development] 4r44444:
Is it possible to add this patches? (Sound/Touchfix For hi12)

https://github.com/kernins/linux-chwhi12
[BLISS ROMS Development] lfom:
Hello, there!

Thanks for your work. I have tested one of your stable builds on a Thinkpad 8 (Baytrail SoC, Intel SST + Realtek I2S Codec) but I also got no sound... I've seen your post in the Android x86 Google group, and I am wondering if only the Bleeding Edge builds have the patches for Baytrail... If yes, what build do you think it's more compatible? Thanks.
[BLISS ROMS Development] electrikjesus:
No, it's only a few specific builds up to this point so far. Most of my baytrail builds are market with the word atom in the file name, so that's usually the dead givaway.

BUT, I tend to think that the no sound issues are usually due to Windows or other OS's not shutting down the hardware properly. Have you tried to power down, boot to bios first, then Bliss?
[BLISS ROMS Development] electrikjesus:
I might be able to do something for that. Assuming I remember when I get a chance to jump back in the kernel.
[BLISS ROMS Development] electrikjesus:
The next few builds I'll be uploading do have NVMe support fixed. So try with those. Coming soon.
[BLISS ROMS Development] lfom:
Yes, many times. The ALSA commands never detect a sound card (recent Android x86 build find only IntelHDMI). The problem seems to be more complex, wrong IRQ mapping and firmware issues:

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

As you said you were building from their tree, I assumed it had all fixes. If you have time, please link to a build that you think it is more up-to-date with Baytrail fixes, I could not locate one in the official repository. Thank you again.

Regards
[BLISS ROMS Development] lucasdeeiroz:
Yes, but it got stuck at 91%. I had to force-close etcher, and the USB was booting ok. No issues yet.
[BLISS ROMS Development] cai_miao:
Ty man, now the thing is: I can't use my touchscreen with the nougat ipts build,

but I found a working modified marshmallow bliss-x86 build shared by japanese site, it's here:

https://drive.google.com/drive/folders/0B3Ttv3AmOdafWTAzTWF5Q3I4R00

I'll try struggling with current build, but if possible, can you investigate if there any problem? ty in adv.
[BLISS ROMS Development] FiendFyre:
Holy crap it works, thank you so much! I've been waiting on an Android build for my SP4 for so long
[BLISS ROMS Development] THEHOLYG0D:
Thank You so much for taking it into consideration...
[BLISS ROMS Development] cai_miao:
though touch works, it's extremely unstable with wifi so use it at your own risk...
[BLISS ROMS Development] FiendFyre:
Seems to be working well enough for now, so I'll take it. Hopefully [MENTION=928479]electrikjesus[/MENTION] can use this to figure out how to add ipts support to his version
[BLISS ROMS Development] Ashwin Prabhunerurkar:
can you share the link of the Japanese website

if this works on my sp4 i will be ecstatic
[BLISS ROMS Development] daWyrd1:
thank you very much kantii. but alas no audio with my hp pavilion x2 12-b020nr detachable. the audio hardware is listed as	B&O Play with dual speakers(??).

if i'm the only one with no audio i am loath to ask for another build. in which case your efforts are appreciated by this beggar.

the kernel 13 that electrikjesus used with his Bliss-v7.2-android_x86_64-OFFICIAL-20170809-0915_k4.13rc4-b_NVMe_01 has been the only nougat that had audio for me.

:fingers-crossed:
[BLISS ROMS Development] cai_miao:
I have already posted the download link in my original post,

if you are looking for the original link, it's on their famous bbs 5ch (formerly 2ch),

link goes here: http://egg.5ch.net/test/read.cgi/android/1463986349/888 (edit: corrected link)

He said that Android 6 with old IPTS driver ( kernel 4.4 ) should work stably ,

though Android 7 with kernel 4.9 works, high graphic load seems making touchscreen ded.
[BLISS ROMS Development] 4r44444:
Sound works too?

Edit not works, doesn't even boot (chuwi hi12)
[BLISS ROMS Development] cai_miao:
sorry man this is for ipts devices (surface pro 4, etc.).
[BLISS ROMS Development] poincare:
Hi bros, been following Bliss x86_64 for awhile as a lurker. Looks reasonably stable now. Just wondering if anyone has solid recommendations for a good hardware tablet for Bliss x86_64 that is affordable and suitable for gaming? Cheers!
[BLISS ROMS Development] z750leovince:
i tested for my surface book but touch screen doesn't work for me.
[BLISS ROMS Development] cai_miao:
please extract system.img from system.sfs, get a linux workaround and mount the img, re-create those symlink to 0076 binaries.
[BLISS ROMS Development] z750leovince:
i don't know how modified this...and i don't have linux in my computer
[BLISS ROMS Development] androidlover420:
A well defined tutorial to dual boot bliss x86 with windows 10 ?????
[BLISS ROMS Development] THEHOLYG0D:
Can you tell which all files, and are those permissions?
[BLISS ROMS Development] cai_miao:
Below commands are for those using Surface Book (firmware 0076),

For Surface Pro 4, firmware 0078 is symlink-ed by default so you don't need to do anything.

You should first pull out system.img from system.sfs, and get a Linux workaround prepared.

On Linux environment, once you mount system.img, run these commands:

# make sure you're now located at the root folder where you mount system.img
cd lib/firmware/intel/ipts/

# delete original symlinks
rm config.bin intel_desc.bin vendor_*

# re-create symlinks to correspond binaries
ln -s iaPreciseTouchDescriptor.bin intel_desc.bin
ln -s SurfaceTouchServicingDescriptorMSHW0076.bin vendor_desc.bin
ln -s SurfaceTouchServicingKernelSKLMSHW0076.bin vendor_kernel.bin
ln -s SurfaceTouchServicingSFTConfigMSHW0076.bin config.bin

If you wish to use the 0079 firmware, change 0076 to 0079 (though I don't know which device is this for)

edit : fix typo

Bliss-x86 IPTS build and that build I posted do have all binaries needed for Pro 4 / Book / maybe else.
[BLISS ROMS Development] electrikjesus:
New Updates for Bliss-x86 are available!! - 10/15/2017

We have added a bunch of updates since our last stable builds. The currently available builds are only x86_64 for the time being since that is the only test machine I have left. If the demand is enough, and we have enough time, we will try to run off a 32bit build with each kernel. Speaking of which, we are releasing a kernel-4.4 version as well as a kernel-4.9 version to help make sure the most people can run what we have.

Updates / Additions:

Added SwiftShader (more info here)

Updated Intel Houdini libraries

Kernel updates (kernel-4.9 builds)

updated NVMe support

Much more (check out github)

Bugs / Issues:

Bluetooth issues still exist on many devices

GPS issues on many devices also

lockscreen might not respond to some trackpad/mouse input (I suggest you disable lockscreen, or if you need it, make it not Swipe.)

There's more I'm sure. The noobs will point it out at least a dozen times ;)

As always, check the Bliss download site for the newest builds. The rest are all on AFH as a backup archive. Hope you all enjoy this one :D

https://downloads.blissroms.com/Bliss/Official/x86/stable/
[BLISS ROMS Development] Guimenez:
i don't understand, The update is for x64 por x86.

Thanks
[BLISS ROMS Development] electrikjesus:
That just means 64bit processors. 80% of the machines available now run one of these, which is why I'm focusing my time on it.
[BLISS ROMS Development] Ashwin Prabhunerurkar:
any chance of including the ipts fix for surface pro 4 in future builds
[BLISS ROMS Development] cai_miao:
I quick glanced at the kernel 4.4 build, it includes ipts binaries so I think it should work. I'm now installing this build to see if it works.
[BLISS ROMS Development] electrikjesus:
No. I tried to make a build with their kernel sources, but it did not work. And there was no attribution or git records in it, and I will not use anything without proper sources.

If you all really want an IPTS build that bad, you're gonna have to figure out a way to get me an IPTS device to develop with.
[BLISS ROMS Development] youling257:
please you built in x86_64 xposed nougat
[BLISS ROMS Development] electrikjesus:
I saw you post a few links to the sources from where you added it. What else did you have to add to include it?
[BLISS ROMS Development] youling257:
i don't understand what your means，only has x86 nougat xposed 88.1，no x86_64

if you no power to build x86_64 nougat xposed，please you build 32 bit Bliss ISO，or 64k32u ISO
[BLISS ROMS Development] electrikjesus:
This was all I was talking about: https://groups.google.com/d/msg/android-x86/J8pUu35VN5g/TDffS7AaAgAJ

Also, I don't know of any build instructions for 64k32u ISO. Please show me
[BLISS ROMS Development] youling257:
Source (for dev):

Xposed ART: https://github.com/PurifyOS/xposed_art_n

Xposed App_process: https://github.com/PurifyOS/xposed_app_process

XposedBridge: https://github.com/PurifyOS/XposedBridge

XposedTools: https://github.com/PurifyOS/XposedTools

https://github.com/rovo89/Xposed

https://github.com/rovo89/android_art/tree/xposed-nougat-mr2

https://github.com/rovo89/XposedBridge

https://github.com/rovo89/XposedTools

https://groups.google.com/d/msg/android-x86/HPc5q9mbS-o/CDiYkW1TDwAJ

---------- Post added at 08:58 AM ---------- Previous post was at 08:55 AM ----------

https://github.com/rovo89/android_art/commits/xposed-nougat-mr2/runtime/thread.cc

https://github.com/PurifyOS/xposed_art_n/commits/aosp-7.1.2_r27/runtime/thread.cc

https://android.googlesource.com/platform/art/+/6c63f863f9dbf734732ff837c1e772b3482e59ff

---------- Post added at 09:04 AM ---------- Previous post was at 08:58 AM ----------

64k32u，https://groups.google.com/forum/#!s...elevance/android-x86/-6nkqz0oUFw/YGcUX3D6CAAJ

https://groups.google.com/d/msg/android-x86/EQR7dqArcXg/17cXjZgoKgAJ
[BLISS ROMS Development] Camlin3:
Is it possible to port Samsung Dex Desktop Launcher to Our Bliss-x86 .Its quiet impressive .

<img src="https://the-gadgeteer.com/wp-content/uploads/2017/09/samsung-dex-110.jpg" alt=DexLauncher />
[BLISS ROMS Development] kamiloxnumetal:
great
[BLISS ROMS Development] THEHOLYG0D:
[MENTION=928479]electrikjesus[/MENTION] I really love the work you are doing and you are having so much of it, I have a Z8350 device, I have rom building experience not that much though, i have the sources for kernel but it's for MM, and I've been using Bliss on my pc for a while now, and now I have a touch screen device. My point here is I'll be trying to build bliss 7.1 using your sources and use either a pre-built kernel or compile new one with old sources, if I get stuc would you mind if ask you noob questions? :3
[BLISS ROMS Development] Guimenez:
i've an Atom Z3735F.

I search on intel site and they say that it's 64 bits.

I will try your latest version :D

Thanks
[BLISS ROMS Development] DiogoSilva48:
If it was open source would be easier but...
[BLISS ROMS Development] Camlin3:
But atleast one can make simulator like that with taskbar like project ditching traditional statusbar
[BLISS ROMS Development] Guimenez:
Try Sentios, it's free
[BLISS ROMS Development] Camlin3:
Thats not satisfactory but today we need more refinement in our ui and ux behaviour which is not upto mark in sentios*

Edit:- Just seen an unreleased version ,looks a little tuned
[BLISS ROMS Development] electrikjesus:
I find Taskbar to be quite suitable for my productivity needs.
[BLISS ROMS Development] Camlin3:
Yeah,that's Fine ,i respect your choice .

But anyway have you any idea for that .

Edit:-I mean Taskbar is barebone but its productivity can be increased with that.

Thanks for OP's reply.
[BLISS ROMS Development] electrikjesus:
New Bleeding Edge Build!! - 10/17/2017

This is an x86_64 build using our kernel-4.12-sp3 as the base, with updated firmware and a few commits to help support the Venue 8 Pro. Also includes all the updates from our Stable releases this week.

So far, all my builds using kernel-4.13-4.14rc5 don't boot for me, so I will not be releasing those until I figure out why. I think I might have to update mesa specifically for those builds, so we will see...

Anyhoo, LINK: https://downloads.blissroms.com/Bliss/Official/x86/bleeding_edge/

EDIT: A 32bit build is on it's way, and I am attempting to build a k64u32 build now. I will update you all if that goes well.

Thanks for the post [MENTION=5550662]youling257[/MENTION]

Update, the k64u32 build completed, hopefully right. I have it uploaded, but if it doesn't work, let me know.
[BLISS ROMS Development] electrikjesus:
Feel free to ask in our Telegram community for Bliss-x86: https://t.me/blissx86
[BLISS ROMS Development] franzli:
Great thanks! I suppose that's for the older baytrail Venue 8 Pro as that's the one you've got if I remember correctly? Will be testing on my cherrytrail DV8Pro as well when I get a chance (may be a while unfortunately, work's a bit crazy at the moment).
[BLISS ROMS Development] electrikjesus:
No sir, those commits are for your model ;)
[BLISS ROMS Development] franzli:
Uuh nice, thanks even more!! I hope I'll get around to testing soon, will make sure to leave feedback! (Unfortunately probably not before November [emoji19] )
[BLISS ROMS Development] THEHOLYG0D:
I found out the technique to make touch work :D, but it's the hard way, after you install on your storage,

get your touch driver, only if it's of silead see and find out, if it is you should go here https://github.com/onitake/gsl-firmware/tree/master/firmware/chuwi

select the correct device and do the below on the main console

su

cd /lib/firmware

rm silead_ts.fw

cp /storage/emulated/0/Download/silead_ts.fw .

chmod 644 silead_ts.fw

reboot
[BLISS ROMS Development] electrikjesus:
Let's hope that I just figured out the easy way for us ;)

https://github.com/BlissRoms-x86/de...mmit/58b1df66e7619445c3b6fb34865187cae7d077f0
[BLISS ROMS Development] electrikjesus:
I ended up removing the latest 32bit & k64u32 iso's from the bleeding edge folder. They ended up not booting right o0n too many machines
[BLISS ROMS Development] youling257:
seem you not fork https://osdn.net/projects/android-x86/scm/git/art/

“ART: Change main-thread thread paging” is important for 4.9 lts/4.13/4.14，also necessary for xposed

---------- Post added at 08:56 AM ---------- Previous post was at 08:40 AM ----------

you can choose revert “mm:” on kernel source，or add “ART: Change main-thread thread paging” to Android art source.

https://github.com/youling257/android-4.9/commits/Sep/mm

https://github.com/youling257/andro...r=f51bda2b0aeba23e5162e38dc2ff69fac45d718a+34

https://github.com/BlissRoms-x86/kernel_common/commits/k4.13rc1-dev

---------- Post added at 08:59 AM ---------- Previous post was at 08:56 AM ----------

http://4pda.ru/forum/index.php?showtopic=650808&view=findpost&p=65160655

---------- Post added at 09:07 AM ---------- Previous post was at 08:59 AM ----------

silead and silead_dmi working on my 4.9 kernel，https://github.com/youling257/android-4.9/commits/Sep/drivers/platform/x86/silead_dmi.c

https://github.com/youling257/android-4.9/commits/Sep/drivers/input

prepare for lib/firmware/silead/*.fw

---------- Post added at 09:17 AM ---------- Previous post was at 09:07 AM ----------

http://bbs.phoenixstudio.org/cn/read.php?tid=10730&fid=12
[BLISS ROMS Development] electrikjesus:
You might as well just take the next step, and fill out an application to join Bliss and help contribute ;) https://goo.gl/forms/PdiaAj1PojosmehK2
[BLISS ROMS Development] Guimenez:
I've tried latest build on my baytrail (Atom Z3735G) but the sound still doesn't work :(

I don't know why, but sometimes the Android stop booting and i need to remove data folder and start everything again.

Is happening with anyone else?

Thanks
[BLISS ROMS Development] electrikjesus:
Yes, sometimes the data.img method has the same issue
[BLISS ROMS Development] lfom:
Thank you for the link. I am trying to download the compressed file, but it's too slow for me to download from Baidu. But I will keep trying. By the way, the Thinkpad 8 I have is model 20BQ001JBR. Best regards.
[BLISS ROMS Development] Guimenez:
What about audio, any news onde that
[BLISS ROMS Development] electrikjesus:
I got nothin
[BLISS ROMS Development] madprofessorus:
I tried it today, build a boot USB flash disk,booted my PC,but it refused to go beyond the setup screen,no Gmail,no New account,it keeps force closes
[BLISS ROMS Development] androidlover420:
How to dual boot bliss x86 with windows 10
[BLISS ROMS Development] ElfinJNoty:
Is because your wifi module is not auto-enabling upon boot. This has been a reported issue with some hardware configurations. The workaround has been posted... Please use the search function in this thread by searching for "SETUPWIZARD=0"

You must first turn on your wifi, log in to an available network, then sign into Google by, for example, opening PkayStore after your Wifi is connected

---------- Post added at 03:02 AM ---------- Previous post was at 03:00 AM ----------

Read the initial post, install instructions, recommended to try the Easy Windows Installer if you are not an advanced partition wizard and want the simplest method ?
[BLISS ROMS Development] cai_miao:
few days ago I also found a nougat x86 build for IPTS devices,

5ch link: https://2ch.live/cache/view/android/1492904063/58

Download: https://drive.google.com/open?id=0B3Ttv3AmOdafQUNhdjE5MWRGVkU

but I haven't make it boot on my SD card,

also the NVMe support seems weird and got a tearing display on my Surface Book.

Not only latest Bliss-x86 but also this build.