yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] IcedCube:
Would the Bliss team be able to point me in the right direction as to how to build my own kernel (and if needed, ramdisk/initrd) to use with Bliss x86? I believe there's some kernel settings missing for Atom x5 Z8350 Cherry Trail tablets. I want to test my own kernel build as there's no audio since mine uses a "Intel SST" sound chip (well, that's what Windows says). I know 4.12 has some support for that, but I need to double check.

I recently got my hands on a Chuwi tablet that's a dual boot x86 Android and Windows OS configuration, but the version of Android that's currently on it is Lollipop 5.1 and that's pretty old. No root either, which means I can't pop Adaway or any other good blocker to stop malicious ads popping up, etc.

I tested an older build of Bliss-x86 7.1.2 (I think?) with the 4.9 kernel, and it ran OK. Not the best thing ever, but it worked - WiFi didn't get detected and not sure about Bluetooth either. Meanwhile 4.12 on the tablet, and WiFi is detected which is excellent. Bluetooth is working as well.

Should go without asking but thank you Bliss team for making magic happen for x86 Tablets and I hope you guys have a wonderful festive season.

------

EDIT: After looking at hardware IDs in Device Manager, I noticed that the sound devices have an entry for a Realtek I2C Codec entry. That ID is ACPI\10EC5651... might grab the Bliss sources and give this a shot.
[BLISS ROMS Development] electrikjesus:
Start with the Android-x86 docs, and fill in the blanks with a few of the posts [MENTION=5550662]youling257[/MENTION] has made in this thread

http://www.android-x86.org/documents/customizekernel
[BLISS ROMS Development] electrikjesus:
For those interested in the process, I ended up streaming the entire bringup to Android-8.1 on Twitch, and the videos are all exported to YouTube here: https://www.youtube.com/watch?v=i72TiOJ6EUY&list=PLp6CAOoRcrWkXaj6m1rDRGxPn_gf1bFXI
[BLISS ROMS Development] IcedCube:
Alright, thanks for that [MENTION=928479]electrikjesus[/MENTION]. Only question I have is what do the kernels mean in your repo? There's heaps of them, and I'm currently basing my kernel on k4.12-cr-sp-ip. I don't know what the suffixes are for, so I just picked the one that looked the most recent.

Compling went fine on my older 16GB RAM Core i5 workstation. The biggest problem was the actual sync of the repo - I thought it would be only a few gigs, but I had to times that by 10 to get more realistic data amounts.

Currently compiling the kernel again since it errored about ipts firmware not being found. After I get back home I'll give my custom build a run.
[BLISS ROMS Development] electrikjesus:
The suffixes are my hints to what commits or sources I merged from. So, k4.12-cr-sp-ip in this case stands for Kernel 4.12, with added commits for Chromebooks, Surface Pro 3/4, and IPTS Touchscreen. I also have added the extra firmware needed for that in the most recent branch I have in device-generic-firmware
[BLISS ROMS Development] IcedCube:
Thanks for that. Are firmware files copied to the filesystem image when the kernel is compiled or is that part of the 'lunch' android build process?
[BLISS ROMS Development] IcedCube:
Alright, I'm getting somewhere. I'm noticing that the avc daemon is blocking a lot of requests to access /dev/dri/card0. Is that normal or do I need to specify a boot parameter to allow that? Seems the animations and stuff aren't hardware accelerated due to AVC blocking requests to those. Seems to output messages about classes not defined in policies?

While I seem to have baked the right codec driver into the kernel and "alsa_amixer" does report there are mixer controls , I still cannot get sound. ALSA keeps saying "ASoC: No backend DAIs enabled for Audio Port". Touchscreen is still not working even though I patched the silead-dmi.c file with my devices firmware file, etc.

I can't check the initial boot log before android boots (well, I can but I have like 5 seconds leeway before the shell gets switched to the bootlogo) because it gets overwritten with all the logs from android's boot process and operation.

EDIT: Managed to figure out what Silead is erroring on. Apparently it can't read the chip correctly for some reason, and I'll be damned if I know why. Some github issues say "answer N to the silead touchscreen option in menuconfig and then select Y on the "tablets with silead touchscreens"... but that just removes that latter option if I say N to silead touchscreens.

silead_ts i2c-MSSL1680:00: Chip ID read error -121
acpi MSSL1680:00: Failed to change power state to D3hot
silead_ts: probe of i2c-MSSL1680:00: failed with error -121

This is a Chuwi H10 Pro tablet. Kernel 4.12. Should I test out the latest alpha build of Oreo and see if that solves anything?
[BLISS ROMS Development] digital0:
Yes, please. I have Onda obook 20 plus, but the latest oreo kernel just reboots here. It would be interesting to know if it boots and works on your tablet.

And there were silead patches in the latest kernel.
[BLISS ROMS Development] Blade McKain:
fix for sound for Chuwi hi10 and hi12

Hi,

it would be possible to insert the fix for sound for Chuwi hi10 and hi12 ?

Thx you
[BLISS ROMS Development] aiglesh:
I tried Oreo based alpha build on New Surface Pro 2017. Unfortunately touch screen doesn't work, i keep getting message that google services stopped. Also no way to to put it in portrait mode even with any app, whenever I tried screen just shrinked from the sides while still being in landscape mode. It never rotated.

I tried it also on Lenovo miix 2 8 tablet. Touch worked but the wifi module was not recognized. This tablet has Broadcom 802.11abgn Wireless SDIO Adapter.
[BLISS ROMS Development] IcedCube:
I gave Oreo a shot and was able to get it to boot fine. Used a custom-built USB with EFI syslinux because GRUB2 caused the tablet to shut off every time it would attempt to boot EFI GRUB.

Touchscreen was no-go, although it did manage to see the chip ID. It was looking for /lib/firmware/silead/mssl1680.fw so I downloaded the firmware from https://github.com/onitake/gsl-firmware/tree/master/firmware/chuwi/hi10_pro-z8350 (mine is a CWI1529, Z8350 variant) and gave it a shot. Managed to make it attempt to load, but threw the error "Initialization Error. Error 0x0" with either firmware. Is that a success error code?

Makes me wonder if we should be using silead driver or gsl1680_acpi? Still no audio though, as ALSA was spewing "No backend DAIs enabled for Audio Port". Seems to be really good hardware acceleration, everything seems to be turbo animations. Some slowdown but that's due to me booting Android off a USB in USB 2.0 mode.

---------- Post added at 05:08 PM ---------- Previous post was at 05:02 PM ----------

@youling257 My chuwi hi10 pro tablet is realtek rt5651 codec. If I get you the output of alsa_amixer, can you provide me with the instructions on how to get the sound working correctly?
[BLISS ROMS Development] digital0:
How did you do that? I'd like to try EFI syslinux instead of grub.

silead definitely. gsl1680_acpi is no longer developed, and its developer recommends using silead.
[BLISS ROMS Development] youling257:
work with sof，https://github.com/plbossart/UCM/commits/master

https://github.com/plbossart/sound/commits/topic/sof-1.0-dev-v4.14

5651 too trouble.
[BLISS ROMS Development] IcedCube:
Sorry, I don't quite follow. Are you saying that rt5651 is causing trouble as well and is being resolved?

On the silead front, hmm. Guess I'll have to extract my firmware from my tablet and give it a shot. Although what is "silead_dmi" then (it's in the kernel under x86 platform device drivers).

As for EFI, here's what I did. I've provided a ZIP to get you started. If you don't trust my files, even though they should be MD5 perfect with the ones from the latest syslinux build, you can check out the UEFI howto on the syslinux wiki. In the zip are shell.efi and shellx64.efi. These come from the EFI Dev Kit v2.0, are completely optional (just happen to be on my USB stick) and should give you access to a MS-DOS like shell if you want to manually investigate boot woes (or fire up binaries at a EFI prompt).

bootloader wise, It's a matter of copying some files from the syslinux archive into their correct places and interpreting a grub.cfg into a syslinux.cfg file.

Then I made a system.img out of the system.sqs file - in bliss 7.x the squashfs file contained a system.img that you could put in the "android" directory of your USB drive but in oreo, it's a complete filesystem with all the system files. I had to make a 3GB system.img with ext4 filesystem on my USB, mount it, unsquashfs the contents of system.sfs into that mounted image, then run "mv squashfs_root/* ." while in the system image root. Ran sync and umounted everything. Unplugged from workstation; booted on tablet. Also has a lot of space to move around in. :good:

So you should have on your USB or whatever the following:

<ROOT>
- android
-- kernel
-- system.img
-- data.img
-- ramdisk.img
-- initrd.img
- EFI
-- BOOT
--- bootia32.efi
--- bootx64.efi
--- ldlinux.e32
--- ldlinux.e64
- (other root level dirs)

If all goes well, after entering your tablet's BIOS you should see UEFI: USB Drive, Partition 1 or something like that. Choose it, and it should say "Booting Android..." followed by "Loading /android/kernel....." and "Loading /android/initrd.img.....". After 5 seconds or so, the screen may flicker and you'll get the kernel bootup log, then eventually the x86_64:/# prompt, then eventually the (unfortunately horribly JPEG'd on my IPS tablet screen) Oreo Bliss logo animation.

YMMV but syslinux worked out of the box where GRUB just shat itself and turned off my tablet.
[BLISS ROMS Development] digital0:
And where should I put syslinux.cfg file?
[BLISS ROMS Development] eqbirvin:
That link gives a 404 error, any chance I can test that installer out for you guys??
[BLISS ROMS Development] electrikjesus:
It got updated, that's all. https://github.com/BlissRoms-x86/Androidx86-Installer-for-Windows/tree/master/bin
[BLISS ROMS Development] 4r44444:
Tryed the newest Oreo Alpha Build on Chuwi Hi12 Tablet.

- >Liveboot does not work - When click on Live Boot a black screen flattering for 1 second and than Tablet restarts.
[BLISS ROMS Development] IcedCube:
Root directory. It should be named syslinux.cfg , not syslinux.cfg.text or anything else
[BLISS ROMS Development] elwhiteboy01:
Been looking for a good android emulator. Installation methods seem to be similar to that of remix os. I'm going to give bliss a shot. I will give feedback eventually. Thanks in advance for your work.

Update, successfully installed bliss through USB. I used a program win32 by sourceforge. I downloaded the ROM in img form. And installed it to the USB through the program. Previously I disabled bitlocker on my windows 8.1 laptop/tablet. Also I disabled secure boot previously. And once the ROM was on the USB I went back into bios and changed the order of boot options to USB diskette first. Then I saved and did a reboot and bliss came up. I selected the first option and voila, Android on my PC. Thanks a lot to the devs. Seems to be working great with Google sign in options. Hope my installation procedure was helpful to others. Have a blessed day.
[BLISS ROMS Development] aiglesh:
@ electrikjesus

Is it possible to address these two issues esp Surface Pro ones? Thanks
[BLISS ROMS Development] TacoLoco:
When I open system.sfs in 7zip, there is not system.img..?

Edit:

I'm trying to install Oreo Release..

Edit2:

Just found the updated Installer which works with your Oreo Build.. You should link it on the second post.. Anyway I'll revert to Nougat for the moment, but looking forward to some stable Oreo Build.. Thank you very much Team Bliss!
[BLISS ROMS Development] electrikjesus:
I really don't want to answer because you didn't even search the thread from the looks of it. You can search the thread like everyone else has to. These have all been answered already.

Q: I tried Oreo based alpha build on New Surface Pro 2017. Unfortunately touch screen doesn't work:

A: Google says it's using IPTS... SEARCH the thread for wtf that means

Q: i keep getting message that google services stopped.

A: This is a known issue also. Stated it in the release updates. SEARCH

Q: Also no way to to put it in portrait mode even with any app, whenever I tried screen just shrinked from the sides while still being in landscape mode. It never rotated.

A: Also a known issue in Oreo Many have mentioned this already. SEARCH.

Q: I tried it also on Lenovo miix 2 8 tablet. Touch worked but the wifi module was not recognized. This tablet has Broadcom 802.11abgn Wireless SDIO Adapter.

A: This is the only one I might give you an answer for. But you need to find out the actual wireless module name first though. That's a generic identifier you gave.
[BLISS ROMS Development] electrikjesus:
It has been mentioned that the Oreo releases use Google's squashfs instead of the one we were using in previous releases. This is why it needs a new installer
[BLISS ROMS Development] aiglesh:
Hi thanks for the reply. You are right I did not search the thread. Sorry for that. :(

About the last one, will get back to you with the answer. Thanks again
[BLISS ROMS Development] IcedCube:
I will update this pot with a "Convert system.sqs to system.img for USB manual installs" when I get to my work station.

---------- Post added at 09:48 AM ---------- Previous post was at 09:43 AM ----------

This is not a Android emulator. This is Bliss running as an Android OS. You won't be able to run Windows apps inside it, this is basically a desktop version of a mobile OS.

If you want a good Android emulator, try Memu or Nox. But that is off topic.
[BLISS ROMS Development] fastguy:
Hi [MENTION=928479]electrikjesus[/MENTION], would you have any findings about how to enable/use multi display feature?
[BLISS ROMS Development] electrikjesus:
It's all pretty vague as to what we need to do there. I've already included this line for extending to secondary displays ( https://github.com/BlissRoms-x86/device_generic_common/blob/o8.1-x86/device.mk#L110 ), but I feel we should also need to add settings for it somewhere, but I'm not able to find it yet.
[BLISS ROMS Development] elwhiteboy01:
Ah, well I guess that's out. No way to use as a dual boot with a flash drive?
[BLISS ROMS Development] aiglesh:
Tried the beta on my windows tablet, Lenovo miix 2 8. Installation was fine but I am stuck at the boot animation forever and had to hard reboot my tablet. I was able to boot alpha version without issues.

Tablet has intel Atom Z3740 CPU, 2 GB of RAM, 64 GB of internal flash storage eMMC and an 8-inch IPS display. Intel's HD Graphics (Bay Trail) is responsible for graphics output.

I used the new UEFI installer. Also tried to boot in live mode by installing it on a FAT32 partition via rufus, same result, I was stuck on boot animation.

It booted fine on my Surface pro 2017 via live USB. However due to absence of IPTS driver touch screen was a no go. Will wait for a version with IPTS driver/ firmware incorporated.
[BLISS ROMS Development] electrikjesus:
Can you please try booting your miix using the old modprobe grub entry as well and report back?
[BLISS ROMS Development] aiglesh:
Ok. Wil try. Thanks
[BLISS ROMS Development] THEHOLYG0D:
Illuminati Confirmed! :D :D :D :D :D :p
[BLISS ROMS Development] LittleHedgehog:
Hello. I am trying to install BlissOS to my Surface Book with a USB. I've created two partitions: 16GB for the OS and 300MB for the Grub. The issue is, The installer can't see the partitions I created. It only shows my USB drive, as sda1. I tried the Detect option but it didnt show my partitions either. The Live boot worked fine btw.

Any luck on how to fix this?
[BLISS ROMS Development] aiglesh:
Unfortunately same result.
[BLISS ROMS Development] bethnesbitt:
Internal storage

I'm using xubuntu 17. Some of the x86 builds see my HDD storage, while, other builds are reading my ram as storage.

I have 250gb EXT4 partition. The v10 12/30 build sees my HDD, but, the stable versions are reading my RAM.

Any suggestions?
[BLISS ROMS Development] elwhiteboy01:
I don't know if I missed it in the OP, but I can't get the Bliss Rom to retain data. I scoured through the posts for a similar topic, but I stopped at around the 66th post. I noticed in the Phoenix OS it has a (data disc img. file). Is this needed to save data so you don't have to sign in to wifi and google each time you start? I didn't see that (data img. file) in the usb folder I used. I did notice it was said to delete the file system.sfs, but to update the SU binary. Once you delete that file is it related to retaining data? Or is there no such option for the Bliss Rom? And also, I have no speaker audio. Bluetooth seems to recognize my headset, but I haven't tried connecting yet. I'm using the HP Pavilion x2 10. Touchscreen works and just about everything else. Except the saving data and speaker output. Thanks in advance for any help or suggestions and HNY.
[BLISS ROMS Development] wizzdome:
Just wanted to drop a note and say thank you for this build... I have an Acer Aspire z all in one touch screen desktop i had thought to install an x86 on. I got frustrated with installs not putting grub up so i deleted my windows installation on the thing and went and installed you x64 pc 10 (i know it is beta) It works great as a solo os though the wifi was having problems with google... youtube however worked fine with no strings on the wifi... (i found traces of mobile data settings in the dev options) It appears to me that the google apps are not set up to communicate off of mobile data which would make no sence if youtube works fine... im dowloading the 8.0 alpha to see how it runs on my system before i try out a stable release... I want you to know though I am grateful you are taking in an x86... this was the first x86 i have run recently that has not froze on me so i am looking forward to checking out the 8.0 (thanks again)
[BLISS ROMS Development] electrikjesus:
In the second post:

Part 3.5 - Using Bliss-x86 from your USB drive

If you so choose to use Bliss from the USB drive, your data will be saved in a temporary state unless you create a data.img to store the data. We can create a data.img in the root dir of the USB drive (make sure you have a minimum 4-5gb free). We suggest using a tool like one from XDA called RMXtools to create it (we suggest you use version 1.7). Check the tool's thread for how to use it, but when you figure it out, you will want to create your data.img inside the root directory of your USB drive, with all the other .img files. From there, just boot into live mode, setup your system the way you want. and the data should be persistent across a reboot now.

For your sound issue, try booting again, and adding AUTO_LOAD=old to the grub entry, just after quiet
[BLISS ROMS Development] maxriter:
IcedCube can you provide menu.c32 or vesamenu.c32 that can be used with this syslinux?
[BLISS ROMS Development] wizzdome:
could you maybe try another set of gapps in pc10 build?

I gave up messing with grub i will use the desktop as an android device... but i just need to get a stable build that wont freeze on me and it seems like the only one not to freeze on me is the one that has problems with google and the internet... (but somehow not youtube) strange....

btw i did install oreo and couldnt get it to boot. so i installed the latest stable which also freezes on me. (i have been playing angry birds evolution) and it frezzes at random times during the game. Also if i leave it sit for a while when i come back it will be frozen as well. (the pc 10 version i have no problems with but gapps do not connect to wifi)
[BLISS ROMS Development] bsorli:
Thanks for the information and notes for trying myself using a ISO boot live USB drive. Plan to check it out and hope it works better then the standard Chuwi android build. Sorli...
[BLISS ROMS Development] aiglesh:
Few comments about the beta version on new Surface pro 2017. It is running very smooth and nice. Very nice work indeed. However

1. The biggest issue for me is that the rotation is not working. No way to put the tablet in portrait mode. Can it be fixed later?

2. I noticed that the back of the tablet was a bit hot during Android session scissors to windows session. Not a big deal but still one can notice it.

3. I wish hardware button(power on/off) works somehow.

4. Not sure if sleep is working or not?
[BLISS ROMS Development] Lovelyven:
Is the touch screen working for the new surface pro with the new bliss Oreo?
[BLISS ROMS Development] aiglesh:
Nope, no drivers yet.
[BLISS ROMS Development] attachsnow:
Hi, I have ASUS T305CA tablet with official android x86 kernel 4.9 rom and have a sound problem.

The audio device is Realtek 274 (rt274). The headphone jack works but speaker no sound.

If I want to try 4.14 kernel in android system. How should I do ? thank you.

感謝
[BLISS ROMS Development] electrikjesus:
Add your HDD as sdcard to grub. example:

SDCARD=sda6
[BLISS ROMS Development] bethnesbitt:
SDCARD=sda

I'm running Bliss 7.2 stable on a separate 80gb HDD, added the following entry:

linux /android-2017-10-14/kernel quiet root=/dev/ram0 androidboot.selinux=permissive buildvariant=userdebug SRC=/android-2017-10-14 SDCARD=sdb2

initrd /android-2017-10-14/initrd.img

also did the same with the instructions given in the beginning of this post, basically tried both techniques.

When I boot into android, it shows an unsupported sdcard, when trying to format it as internal, there is an error. Partitioned the 80gb sdcard, android on 6gb, sdcard partion on a fat32, also, tried on a ext4, am still getting the error.
[BLISS ROMS Development] electrikjesus:
Can you let me know what kind of drive it is? I will look into it further from there
[BLISS ROMS Development] bfmetcalf:
I have the Bliss V8.0 Alpha running fine on my Dell Inspiron 7348. When trying to get either of the V10 builds to work, they just get stuck at the bootanimation, I have left it for an hour and they never move on. I am booting with the same exact grub entries (edited the SRC= and DATA= parts). What is the best way to troubleshoot this?
[BLISS ROMS Development] fguy:
Why did the removal of android 8.x branches from your repository (github.com/BlissRoms-x86) happen?
[BLISS ROMS Development] bethnesbitt:
It's a SSD sata III mounted in a desktop. I'm wondering if Linux mint is blocking Android sharing, Enabled share got the same error as an 8 instead of a 10. Might try Ubuntu dual boot next just to see what happens.
[BLISS ROMS Development] wizzdome:
if i am reading this right your android system is on the same drive your trying to format? try leaving it as external?
[BLISS ROMS Development] electrikjesus:
I will be making the "Official" announcement later on today in a State of Bliss post, but here is the gist of it:

There is also news regarding Bliss OS for PC. Recently, we found evidence of paid projects outside of Bliss Family using our hard work without bothering to keep attribution or credits to us or the original authors. This is not acceptable to us at Bliss. We strive for innovation and to push Android forward. When others take it upon themselves to not only raid our repos for solutions and re-author those solutions as their own, but then to charge for their services or releases based on our hard work, we have to take a stand. Due to this, and the attention Bliss OS for PCs has been getting from potential investors, we feel it is best to switch our PC builds to a private repo for development.

This doesn’t mean that we won’t be releasing the source. It means that for the time being we are keeping the source behind closed doors, and when we are ready, we might decide to release the source for the previous release. So in light of this change, we have removed sources from GitHub for our Oreo 8.0 & 8.1 branches. This has been done to help protect our intellectual edge as well as our potential investors piece of mind.

We have already done what many wrote off as impossible or far too much work, making one source that can build an Android-x86 based ISO, an Android-IA based ISO, Emulator images, AndroidTV based release, as well as the traditional Android device update.zip